JP4407650B2 - Blog creation client device, blog server, and programs thereof - Google Patents

Description

  The present invention relates to a blog creation client device, a blog server, and a program thereof used in a content update system capable of updating the description content of a blog on a server using a web browser. In particular, the present invention relates to a technology for reflecting a history of content actually reproduced by a blog creator on a blog.

In recent years, with the development of communication networks such as the Internet, anyone has opened a personal homepage (Web page) on the Internet, and the user has his / her profile, hobbies or interests on the opened homepage. The information can be provided widely and generally. Not only that, but also by adding chat and bulletin boards and disclosing e-mail addresses, it becomes possible to communicate with many people with common hobbies over the Internet. Yes. Generally, users need knowledge of specialized technologies such as HTML (HyperText Markup Language) in order to create their own homepages. In recent years, in order to send information to more users, web pages have been created. 2. Description of the Related Art A content update system that can easily update the description content of a page on a server using a web browser (WWW (World Wide Web) browser) that is software for browsing. For example, if you use a certain content update system called "Blog Tool", it is called a so-called blog or weblog that can be easily updated on a daily basis even for beginners of the Internet. A simple diary-like site (blog site) can be created with good appearance, and the created blog can be opened on the Internet. For example, a technique described in Patent Document 1 or Patent Document 2 shown below is known as a related to such a content update system.
JP 2002-183036 A JP 2005-190431 A

  By the way, a blog creator (so-called blogger) who establishes a blog is interested in content such as music and movies that he / she has viewed on the blog by placing the title, title, or image of the song. Communication with other users becomes easier. However, in the past, it was necessary for bloggers to input the content that they wrote on their blogs using a personal computer terminal, etc., and playback of content such as music and movies that bloggers actually listened to or watched using content playback devices etc. If you wanted to reflect your history on your blog, you had to enter that history separately by date. For example, the technology described in Patent Document 1 enables a chat user to display a history of games played in the past when attempting communication between users through chat or the like. The chat user himself / herself has to manually input the game history. In this regard, the technique described in Patent Document 2 analyzes a sentence posted on a blog or the like, and extracts and displays matters recommended for the sentence (specifically, keywords included in the sentence). Like to do. However, such a display is a result of analyzing the input sentence to the last, and the user has to input the sentence considering the keyword. Therefore, using the above-mentioned conventional technology, it is difficult to “post easily the daily music and movies that bloggers actually listened to and watched before updating the blog”. However, it has been desired that a blogger can easily put information (playback history) about music or video actually viewed by a blogger himself using a content playback device. Not proposed.

  The present invention has been made in view of the above points, and a blog creation client device, a blog server, which can easily reflect the reproduction history of content actually viewed by a blog creator on his blog, And it aims at providing the program used for them.

The blog creation client device according to claim 1 of the present invention is a blog creation client device that edits a predetermined blog site managed by a blog server that is communicably interconnected via a communication network. An entry input means for inputting a blog entry to be reflected on the site, a storage means for storing entry information for registering the input blog entry in the blog server, a plurality of contents, and any of the contents From a predetermined content reproduction unit that reproduces the specific identification information corresponding to the reproduced content as reproduction history information together with the date and time when the content is reproduced, according to an instruction from the user. An acquisition means for acquiring the accumulated reproduction history information, and the acquired Based on the raw log information, and generating means for generating a single history entry information for each date of the reproduction date and a list of contents reproduced at least reproduction date and regeneration day, history entry information described above generated, and the storage Registration means for registering to the blog server regardless of whether or not the blog entry is input based on the entry information.

According to this invention, history entry information including at least a reproduction date and a content list reproduced on the reproduction date based on the obtained reproduction history information is acquired from the content reproduction unit according to the content reproduction. Is generated per reproduction date (that is, one entry per reproduction date) . Then, the generated history entry information is registered in the blog server regardless of whether or not the blog entry is input based on the entry information for registering the blog entry input by the user himself / herself in the blog server. As a result, the blog creator does not bother to create a blog including the playback history of the content entered by himself / herself as the playback history of the content actually viewed by the content playback unit, but to create one entry for each playback date. according to the entry information, so it can easily be ready to browse the entries to reflect and to the date of the blog to the appropriate entries based on the music of the history of the play on the day there is a blog author.

The blog server according to claim 2 of the present invention is a blog entry record corresponding to each of a plurality of blog creators, and means for interconnecting the blog creation client device via a communication network so as to communicate with each other. Includes a first storage means for storing information including a blog entry input by a user in an identifiable manner based on identification information previously assigned to each blog creator, and a playlist entry corresponding to each of a plurality of blog creators An identification given to each blog creator in advance , wherein each record includes history entry information including at least a reproduction date and a list of contents reproduced on the reproduction date, one for each date of the reproduction date . From the second storage means for accumulating identifiable by information, and the connected blog creation client device; In addition, a means for receiving a blog entry request including a blog entry, and a blog entry record corresponding to the received identification information from among those stored in the first storage means in response to the reception of the blog entry request Means for storing the received blog entry; means for receiving a playlist entry request including history entry information together with the identification information from the connected blog creation client device; and receiving the playlist entry request In response, the means for accumulating the received history entry information in a playlist entry record corresponding to the identification information stored in the second storage means, and a predetermined identification from the connected blog creation client device Blogs for viewing blog sites corresponding to information In response to the reception of the received blog browsing request, the blog entry record of the corresponding identification information is read from the first storage unit, and the playlist entry record of the corresponding identification information is Means for reading from the second storage means, and means for returning a combination of the read blog entry record and the playlist entry record to the connected blog creation client device as a response to the blog browse request. Have. According to this, for each blog creator, an entry based on the history information of the content, in particular, the history of the music played on a certain day by the blog creator, is applied to the blog of the corresponding date according to the history entry information that is one entry per playback date. Can be reflected automatically.

  The present invention can be constructed and implemented not only as a device invention but also as a method invention. Further, the present invention can be implemented in the form of a program of a processor such as a computer or a DSP, or can be implemented in the form of a storage medium storing such a program.

  According to this invention, in addition to the registration of the blog entry input by the blog creator himself to the blog server, the playback history of the content played back by the content playback unit is registered in the blog server. Even if the user does not enter manually, the blog creator can easily reflect the playback history of the content actually played by the content playback unit on his blog. Play.

  Embodiments of the present invention will be described below in detail with reference to the accompanying drawings.

  FIG. 1 is a system block diagram showing an overall configuration of an embodiment of a content update system including at least a blog creation client device and a blog server according to the present invention. Of course, the content update system may have hardware other than that shown in FIG. 1, but here, the case where the minimum necessary resources are used will be described.

  The content update system shown in this embodiment includes a blog server BS that provides a blog service for a plurality of users, and a user system A (Ua: for blog creation) that a blogger uses to create / update a blog site (hereinafter simply referred to as a blog). Client apparatus), general user system B (Ub) and user system C (Uc) used by other users who are not bloggers to browse blogs, and music providing content distribution services for selling and distributing music data As appropriate, the distribution server MS and the affiliate program site AS providing the affiliate service are capable of bidirectional communication via an existing wired or wireless communication network X such as a public telephone network, the Internet, or a LAN (Local Area Network). It is a system connected to. In this embodiment, various data and programs described in the drawings are stored in a “storage unit” of a server (site) or a user system, and the “control unit (CPU)” of the server or user system stores the stored program. Execute processing according to the above, read and write various data, and input text information such as URL (Uniform Resource Locator) and blog entry using input means such as a keyboard as necessary, and communication means Data is exchanged with each other via a modem or LAN interface. Each of these devices has a control means comprising a CPU, ROM, RAM, etc., an input means such as a keyboard and buttons, a display means such as a display, a mass storage means such as a hard disk (HDD), or a nonvolatile memory such as a flash memory. Since it is configured by an independent computer including a communication unit such as a memory and a LAN and can be described as using a known hardware configuration, the description is omitted here.

  User systems A (Ua) to C (Uc) are personal computer terminals (personal computers), mobile communication terminals such as mobile phones and PDAs, mobile game devices, and the like, and are network addresses composed of predetermined character string information By specifying the URL, it is possible to access the blog server BS and the music distribution server MS connected on the communication network X and receive the services provided by the accessed servers. Transmission / reception of various information and the like between each user system A (Ua) to C (Uc) and the blog server BS or the music distribution server MS is, for example, a predetermined software program such as an Internet browser. It is done using.

  In particular, in the user system A (Ua) used by the blogger, it is possible to easily update the contents of the blog on the accessed blog server BS using the browser software after accessing the blog server BS. It has become. Such a user system A (Ua) is a CD, DVD, DVC, or other playback device that reads and plays back media data, or an input device that captures the output from an external device that plays back and outputs these media data (eg, IEEE1394 terminal or USB terminal) And related software). For example, a hardware device such as a portable music player PL can be externally connected to the input device as an external content playback unit, and the user system A (Ua) is connected to the connected external device via the input device. The history information (playback history information) of the content played by the player PL can be acquired from the portable music player PL. A detailed description of the above-described functions of the user system A (Ua) will be described later (see FIG. 3 described later).

  The blog server BS displays page description information on the blog editing screen in response to an access request from the user system A (Ua), and a blog browsing screen in response to an access request from the user systems B and C (Ub, Uc). This is a server computer that returns the page description information to each accessing user system. The page description information on the blog editing screen is provided with an input area for inputting an article (so-called entry) to be posted on the blog, and the article input in this input area is uploaded to the blog server BS. And stored in the blog entry database DB1 or the reproduction list entry database DB2. Articles input in the input area are articles such as profiles and posted texts on the “blog display screen” (see FIG. 2 to be described later), which are entered by bloggers and directly entered and registered. And a history entry that is automatically generated and registered as a history of music data actually played by the blogger on the portable music player PL. Upon receiving each of these entries, the blog server BS accumulates and stores the blog entry as a blog entry record in the blog entry database DB1 and the history entry as a playlist entry record in the playlist entry database DB2 for each blogger. To do. When a blog display screen is presented in response to a blog browsing request from the user systems B, C (Ub, Uc), etc., these entry records stored in the blog entry database DB1 and the playlist entry database DB2 are stored. Refer to the blog display screen that reflects the playback history of the content. Each of the entries may be converted into a format that specifically defines a display form such as an HTML format when the entries are stored in the blog entry database DB1 or the playlist entry database DB2. When presenting the display screen, the display mode such as the HTML format may be converted into a specifically defined format.

  The music distribution server MS stores a large number of music data that can be distributed to the user systems A (Ua) to C (Uc), and based on data distribution requests from the user systems A (Ua) to C (Uc). The server computer distributes the corresponding music data via the communication network X. The affiliate program site AS is a server computer that manages a so-called affiliate, which is a mechanism for paying a predetermined reward to a blogger of a blog that is routed when the music data is purchased from the music distribution server MS via the blog. It is. Since the processing related to data distribution realized by the music distribution server MS and the processing related to the affiliate realized by the affiliate program server AS are well-known techniques, description thereof is omitted here.

  Here, the page structure of the blog display screen presented by the blog server BS in response to the blog browsing request will be described with reference to FIG. FIG. 2 is a conceptual diagram showing an example of a “blog display screen”.

  As is conventionally known, when a blog browsing request is made from each user system to a blog server BS that follows a predetermined URL using a WWW browser, a “blog display screen” as shown in the figure is displayed on the display in each user system. Is displayed. The page configuration of the blog display screen shown in FIG. 2 can be broadly divided into a blog title display section T, a calendar display section CH, a blog display section BH, and other information display sections NH. The blog title display section T displays the title that the blogger himself gave to the blog. The calendar display unit CH displays a calendar of the current or past month, and a hyperlink to the article is set on the date when the article is posted among the dates in the calendar. Therefore, when a user clicks on a date that is hyperlinked in the calendar display portion CH, an article posted by a blogger on the corresponding date as a link destination is displayed on the blog display portion BH. The blog display unit BH displays the latest articles posted in order from the newest date or past articles posted on the date clicked on the calendar display unit CH.

  In the blog display section BH, in addition to a display section that displays articles actually written by bloggers, a playback history display section RH is provided in association with each display section. In the reproduction history display section RH, a music list automatically generated based on the content reproduction history acquired from the portable music player PL or the like is displayed as “<Today's music >>” by a song name or the like for each song. The Further, in the music list displayed on the reproduction history display unit RH, a hyperlink to the music distribution server MS including identification information unique to the music (referred to as a music ID) is set for each music. The user can access the linked music distribution server MS by clicking on the displayed music name, and a music distribution screen or a music preview screen (not shown) provided by the accessed music distribution server MS. )) Can jump the display. Processing related to the display of the music list on the reproduction history display unit RH will be described later.

  As described above, in the music list displayed on the reproduction history display unit RH of the blog display screen, a hyperlink to the music distribution server MS is set in association with each music name. Furthermore, a definition relating to a link to the affiliate program site AS is also described. An example of a conventionally known format of such a hyperlink is that the “target site URL” and the “blog server site URL” are combined as parameters with respect to the “affiliate program site URL”. . Specifically, it is described as "http: // affiliate / jump? Http: //target/...+http: // base / ..." and "http: // affiliate / jump" Corresponds to “Affiliate Program Site URL”, “http: // target / ...” corresponds to “Target Site URL”, and “http: // base / ...” corresponds to “Blog Server Site” This is a description corresponding to By providing such a hyperlink, the target URL site (music distribution server MS in this embodiment) becomes the base URL site (in this embodiment, identification information unique to a blog and a blogger (this is called a blogger ID). )) Via the sale of the product (in this example, song data corresponding to the song name (song ID) in the song list displayed on the blog) A predetermined reward can be paid to the blogger. The process of paying a reward in accordance with the purchase of a product via such a link is performed by the affiliate program site AS. However, since such a process by the affiliate program site AS is known, the description thereof is omitted here.

  Other information display section NH, such as the blogger's own profile, categories that classify articles by genre, bookmarks to blogger recommended / favorite sites, monthly archives (past articles), impressions and opinions of users who called articles Other latest entries and advertisement information other than those displayed on the blog display section BH, such as the latest comments, the latest trackbacks that link to the articles of users who have written articles related to the displayed articles, or advertising banners Various information is displayed. The display position of each display unit on the “blog display screen” is not limited to the illustrated example. Needless to say, if the entire blog display screen cannot be displayed on the display at a time, the blog display screen can be scrolled in accordance with the operation of an up / down direction button (not shown).

  As described above, the user system A (Ua) shown in FIG. 1 is a client device for creating a blog, and uses a WWW browser in addition to a data distribution function for receiving distribution of music data from the music distribution server MS. Of course, a desired blog can be browsed by accessing the server BS, and a blog editing / browsing function capable of editing a blog opened by itself on the blog server BS is provided. Thus, each function of the user system A (Ua) will be described with reference to FIG. FIG. 3 is a functional block diagram for explaining the data distribution function and the blog editing / browsing function. However, here, there are respectively illustrated a configuration in which an independent portable music player PL is externally connected to the user system A (Ua) and a configuration in which the music player function is built in the user system A (Ua). Separately described.

  FIG. 3A is a functional block diagram in a configuration in which an independent portable music player PL is externally connected to the user system A (Ua). First, the data distribution function will be described. The user system A (main body Ua) can receive distribution of desired music data from the music distribution server MS, and the distributed music data is stored in storage means (not shown) such as a hard disk. ). When the portable music player PL is externally connected to the user system A (Ua) via the input device, the music data storage D for storing the music data of the portable music player PL and the storage means are stored by the synchronization software SW. The delivered music data is synchronized, and the music data not stored in the music data storage D is sent to the portable music player PL. By doing so, the music data stored in the user system A (Ua) and the portable music player PL are always matched.

  The portable music player PL has a content playback function for playing back music data stored in the music data storage D in response to a user operation, and plays history information (see FIG. 4A to be described later) in response to music data playback. Reference) is generated and stored in the reproduction history storage means R. When the portable music player PL is externally connected to the user system A (Ua), the synchronization software SW acquires the reproduction history information stored in the reproduction history storage means R from the connected portable music player PL. Based on this, the reproduction history information for sending (see FIG. 4B described later) is generated and held.

  Next, the blog editing / browsing function will be described. When the blog server BS is accessed from the user system A (Ua) using the WWW browser WB, a blog desired by the user can be browsed from among a large number of blogs managed by the blog server BS. In addition, among the many blogs managed by the blog server BS, bloggers can easily edit the contents of the blog by directly entering articles on the WWW browser WB. it can. That is, the WWW browser WB functions as an entry input unit for inputting description contents (blog entry) to be reflected in the blog. In this case, a predetermined management screen (not shown) is displayed on the display in order to prompt the user himself / herself to describe the content on the blog, and the content described on the blog input on the management screen is displayed on the blog server BS. Register with Such an operation is performed through predetermined entry information between the blog server BS and the user system A (Ua). When the WWW browser BS is started and the blog is edited, the reproduction history information for sending (history entry) generated and held by the synchronization software SW is appropriately transmitted to the blog server BS based on the entry information. To do. In the blog server BS, the blog entry which is an article directly input by the blogger on the “blog display screen” (see FIG. 2) is sent to the blog entry database DB1 as an article of the reproduction history of the music data automatically generated. The reproduction history information (history entry) is stored in the reproduction list entry database DB2. As described above, the synchronization software WS performs the distribution / synchronization function of the music data, and also imports the reproduction history from the portable music player PL and the server registration function of the retrieved reproduction history to the blog server BS. To do.

  FIG. 3B is a functional block diagram in a configuration in which a music player function is built in the user system A (Ua). When this configuration is compared with the configuration in which the portable music player PL is externally connected, as shown in the figure, the music data storage D and the reproduction history storage means R included in the portable music player PL are the user system A (Ua). And are managed by the music player PP. The music player PP (content playback unit) has a music data playback function for reading music data from the music storage D and playing it in the same way as the portable music player PL. In addition, it has the same function as that of the synchronization software SW. That is, the music player PP is implemented when a control means such as a CPU executes a predetermined software program. The software program has a music data distribution function, a music data distribution / synchronization function, and a reproduction history server registration function. including. Since the operation of each of these functions is the same as that in the case of FIG. 3A that has already been described, description thereof is omitted.

  The music player PP can be implemented not only in the form of computer software but also in the form of a microprogram processed by a DSP (digital signal processor), and is not limited to the form of this type of program. You may make it implement with the form (what is called module) of the dedicated hardware apparatus comprised including a circuit, an integrated circuit, a large-scale integrated circuit, or a gate array.

  Next, the playback history information generated by the portable music player PL based on the playback history information generated from the playback of the music data and the playback history information acquired from the portable music player PL connected to the user system A (Ua). Each data structure will be described with reference to FIG. 4A is a conceptual diagram showing an example of the data structure of the reproduction history information, and FIG. 4B is a conceptual diagram showing an example of the data structure of the transmission history information.

  As shown in FIG. 4A, the reproduction history information represents a “reproduction date and time” representing the date and time when the music data was reproduced by the portable music player PL, and a unique identification number assigned to the reproduced music data. “Music ID”, “Music name” indicating the music name of the music to be played with the music data, “Playing designation flag” indicating whether or not the music has been played by direct designation, etc. are played as a set of records. The data is stored in descending order. In other words, a record is added every time the music is reproduced by the portable music player PL, and N records are stored when the music data is reproduced N times. In addition, when a record is added, the music data that has been played is added and stored so that it becomes a new highest record, so the most recently played music among the records stored in the highest record It is a record relating to data, and is a record relating to music data reproduced in the past in the record stored in the lowest record. The above-mentioned record has contents adapted to the display order determination conditions exemplified below. Needless to say, the record contents may be appropriately changed according to the display order determination conditions.

On the other hand, as shown in FIG. 4B, the transmission reproduction history information is “based on the acquired reproduction history information” for each “history generation date and time” representing the date and time when the transmission reproduction history information is created. This is data formed by storing “reproduction date”, “music ID”, “music name” and the like as a set of records. One set of records composed of the combinations for each “history generation date and time” is included in the order of display on the blog display screen. The display order to be displayed on the blog display screen is determined according to the following predetermined conditions.
(1) Music with the highest number of playbacks is higher.
(2) The music with the newest playback date is the top.
(3) Music played by direct designation by a blogger (that is, music that is not randomly played) is ranked higher.
The display order is determined according to the descending order of the weighted points according to the above criteria. According to this, even if N pieces of data are included in the reproduction history information, N pieces of data are not necessarily stored for each “history generation date and time” in the reproduction history information for sending. In the above description, it is assumed that M pieces are included.

Note that the reproduction history information updated / accumulated by the portable music player PL may span a plurality of reproduction dates. In such a case, the reproduction history information transmitted to the blog server BS is ranked for each reproduction date, and the reproduction history information for sending is set as “blogger reproduction ranking” for each of a plurality of reproduction dates.
Needless to say, the sending reproduction history information is generated so that the same data does not overlap on the same reproduction date.

  In some cases, the reproduction history information is acquired from the portable music player PL a plurality of times on the same day, and the generation of the reproduction history information for sending may be performed a plurality of times. Therefore, the playback history information for sending does not use the playback history information acquired from the portable music player PL as it is, but without duplicating records included in the playback history information once acquired by the synchronization software SW each time. After accumulating, ranking and shaping are performed based on the accumulated history information, and history information corresponding to a predetermined number of reproduction history dates that are continuous or discontinuous is transmitted to the blog server BS as reproduction history information for sending. It is desirable to do so.

  Next, processing related to the display of the music list (content list) on the playback history display unit RH on the blog display screen is divided into processing on the blog creation client device (user system A) side and processing on the blog server BS side. explain. The processes executed on the user system A side will be described with reference to FIG. 5 and the processes executed on the blog server BS side will be described with reference to FIGS. FIG. 5 is a flowchart showing an example of “synchronous software processing” executed on the user system A side. However, here, a configuration in which the portable music player PL is externally connected to the user system A as shown in FIG. 3A will be described as an example.

  In step S1, initialization is performed. Examples of the initial setting include fetching the contents of a music data library (not shown) stored in the user system A, generating a screen or window, or setting an initial display state. In step S2, it is determined whether or not the music player PL is online, that is, connected to the user system A and in a state where data communication is possible. If it is determined that the music player PL is online (YES in step S2), synchronization with the music storage D is executed (step S3). That is, the music data stored in the portable music player PL and the music data stored in the user system A are synchronized, and the music data stored in the user system A and the portable music player PL are matched. Step S4 determines whether or not a predetermined “sync” button has been pressed. If it is determined that the “sync” button has been pressed (YES in step S4), reproduction history information is read from the portable music player PL in the online state (step S5). Then, when the reproduction history information is read, the reproduction history information for sending is generated and held based on this (step S6). The “sync” button is, for example, a panel switch displayed on a display (not shown) in response to activation of the synchronization software. When the “sync” button is operated by the user, the connected portable music player PL The process of reading the reproduction history information from the above and generating the reproduction history information for sending is executed.

  Step S7 determines whether or not the network is online, that is, whether or not the user client A (Ua) and the blog server BS are accessible to each other via the communication network X. If it is determined that the network is online (YES in step S7), it is determined whether or not there is transmission reproduction history information created on the user client A side (step S8). If there is sending playback history information (YES in step S8), the blog setting, that is, the user of the user system A is registered as a blogger in the blog server BS, and the sending playback history information is stored in the blog server BS as a history entry. It is determined whether or not registration is possible (step S9). That is, it is determined whether or not a user ID, reproduction history update URL information, and the like for registering a history entry in the blog server BS are set in step S12 described later. If the blog is set (YES in step S9), the transmission reproduction history information is transmitted to the corresponding blog server BS based on the entry information (step S10). When the transmission of the reproduction history information for sending is completed, the transmitted reproduction history information is deleted (step S11).

  In step S12, other processing is executed. Other processing includes processing such as purchase of music data from the music distribution server MS, which is an original function, and browsing and organizing distributed music data, in addition to an end instruction. In addition, a process of setting and registering a blog entry such as a text to the blog server BS based on the entry information is performed. Setting registration items in this case include a blog update URL and a playback history update URL (a blog update URL and a playback history update URL to which sending playback history information is sent are different URLs), There are a user ID (blogger ID) and a password in the blog service. If an end instruction has been issued as another process, the process ends. On the other hand, if an end instruction has not been issued, the process returns to step S2 and the processes from step S2 to step S12 are performed. Run repeatedly.

In the “synchronization software processing”, reading of the playback history information from the portable music player PL and generation of the playback history information for sending (see step S5 and step S6 above) are performed without operating the “sync” button. Alternatively, it may be automatically performed in response to the online state detection of the portable music player PL.
In the case where the music player PP shown in FIG. 3B is built in the user system A, the above-mentioned “synchronization software processing” itself is included as a partial function of the music player PP. Processes related to the online state detection of the portable music player PL up to step S6 can be omitted. However, even in this case, the sending reproduction history information must be generated. Therefore, the sending reproduction history information is generated every time the reproduction history information is updated, or the online state detection of the network in step S7 is performed. Sometimes it is sufficient to generate the reproduction history information for sending. Further, transmission of the reproduction history information for sending to the blog server BS may be performed at the same time or before or after registration of the blog entry according to user input such as a text periodically or at the time of blog setting.

  Next, processing on the blog server BS side regarding the display of the music list (content list) on the reproduction history display unit RH on the blog display screen will be described. Processing such as browsing / editing of a blog to the blog server BS from the user client A (Ua) side is performed according to generation / transmission / response of query information by form input using a generally known WWW browser. That is, it is necessary to make a request according to necessary processing to the blog server BS. Here, when a request for information registration is made to the blog server BS (a registration request for reproduction history information for sending may or may not be made at the same time) or a request for browsing the blog is made, the blog server BS Each process executed on the side will be described with reference to the drawings.

  6 to 8 are flowcharts showing an embodiment of each process executed on the blog server BS side. Each of these processes is a program that is appropriately started in the blog server BS, and is always in a predetermined standby state after the program is started. When a request is received from the user client A (B to C), a process corresponding to the request is performed. Execute. Here, FIG. 6 shows a “blog update URL process” that starts when an information registration request (blog entry request) is received, and FIG. 7 shows a registration request for reproduction history information for sending (playlist entry request). FIG. 8 is a flowchart showing an example of “playback history update URL processing” that starts executing when the blog is received, and FIG. 8 shows an example of “blog display processing” when a blog browsing request (blog browsing request) is received.

  The user system A (blog creation client device) displays a blog input page (not shown) on a display by a WWW browser, and uses the blog input page to make a request for information registration by a CGI (Common Gateway Interface) query or the like. Notify the blog server BS. When the blog server BS receives an information registration request, it first fetches query data as shown in FIG. 6 (step S21). This query data includes a user ID (blogger ID) and body data (text data) input on the blog input page. The text data includes a display formatting symbol. A step S22 specifies a user ID according to the fetched query data. In step S23, the entry (blog entry) of the text data received together with the reception date and time is added to the blog entry record corresponding to the user ID stored in the blog DB (here, the blog entry database shown in FIG. 1). .

  The user system A (blog creation client device) performs the above-mentioned “synchronous software processing” (see FIG. 5), and sends it simultaneously with the information registration request so that the reproduction history information for sending is registered in the blog server BS. The blog server BS is notified of the registration request for the reproduction history information. When the blog server BS receives the registration request for the reproduction history information for sending, as shown in FIG. 7, first, query data is fetched (step S31). This query data includes a user ID (blogger ID) and sending reproduction history information (see FIG. 4B). Then, a user ID is specified according to the fetched query data. (Step S32). In step S33, the history entry (playlist entry record) received together with the date / time information added to the playback history is added to the record corresponding to the user ID in the blog DB (here, the playlist entry database shown in FIG. 1). .

The database to which the history entry is added may be the same as the database to which the above-mentioned body data entry is added (specifically, another field in the same database), or the database to which the body data entry is added. Another database (the playlist entry database shown in FIG. 1) may be prepared in advance, and only the history entry may be stored in the separately prepared database in association with the user ID.
If a history entry with the same user ID / date has already been stored in the database, the already stored entry may be updated with the newly received content, or the newly received entry may be updated. You may make it maintain the entry already received disregarding.

  The user system A (blog creation client device) accesses the blog server BS using a WWW browser and notifies the blog server BS of a blog browsing request. This blog browsing request includes a user ID (blogger ID) and a display date. When receiving the request for browsing the blog, the blog server BS first fetches query data as shown in FIG. 8 (step S41). A step S42 specifies the user ID and date according to the fetched query data. In step S43, a text entry (blog entry record) of a specified date corresponding to the user ID of the blog DB (blog entry database shown in FIG. 1) is read.

  Step S44 determines whether or not history entries (playlist entry records) corresponding to the same user ID and date are stored in the blog DB (playlist entry database shown in FIG. 1). If it is determined that there is a corresponding history entry (YES in step S44), the history entry is added to the end of the body entry (step S45). Here, if necessary, blog entries for one week or several days may be read for a blog display screen for one page. A step S46 shapes the display information. That is, the format of each read entry is formatted for the blog display screen. Format data formatting is a format that specifically defines the display mode such as HTML, and includes selection of font type, typeface, size, decoration, hyperlink setting, and the like. The display format of the blog entry is input and specified in advance by a blogger (using a blog input page (not shown)) as a formatting symbol such as a tag. The hyperlink set in the character string of the song name displayed in the playback history display part RH (see FIG. 2) of the blog display screen is “URL of music distribution site & URL of this blog server site & song ID”. Become. Step S47 issues a response. As described above, the formatting of the format may be performed when each entry is registered in the database (step S23 or step S33).

In the above-described embodiment, the reproduction history is formatted on the client side. However, the present invention is not limited to this, and the reproduction history information acquired from the portable music player PL is directly transmitted to the blog server BS, and the blog server BS side A corresponding process for shaping the reproduction history may be performed.
Note that only the playback history is entered in the blog server BS. In addition, the total number of music playbacks, total playback time, and the like are counted for each date, and are entered into the blog server BS together with the playback history. You may make it display by adding to a text.
When a so-called Web-based system is not assumed, that is, when a dedicated protocol or the like is used between the user system (blog creation client device) and the blog server BS, the push type is not limited to the above embodiment. The blog server BS may automatically fetch the playback history information from the user system (blog creation client device) side.

  In the above-described embodiment, an example has been shown in which music data is targeted as the content for which the playback history is placed on the blog. However, the present invention is not limited to this, and the content includes communication such as video data, audio data, text data, and other data. Any data that can be distributed via the network X may be used. When these playback histories are automatically reflected in the blog, the playback device connected (or built in) to the user system A is not limited to the portable music player, but is a playback device corresponding to each data type such as an HDD recorder. Needless to say.

1 is a system block diagram illustrating an overall configuration of an embodiment of a content update system including at least a blog creation client device and a blog server according to the present invention. It is a conceptual diagram which shows one Example of a blog display screen. FIG. 3A is a functional block diagram for explaining a data distribution function and a blog editing / browsing function. FIG. 3A shows a case where the portable music player PL is externally connected to the user system A. FIG. Shows a case where the music player function is built in the user system A. FIG. 4A is a conceptual diagram showing an embodiment of each data structure of reproduction history information and sending reproduction history information. FIG. 4A shows reproduction history information, and FIG. 4B shows sending reproduction history information. It is a flowchart which shows one Example of the "synchronous software process" performed by the user system A side. It is a flowchart which shows one Example of a blog update URL process. It is a flowchart which shows one Example of reproduction | regeneration log | history update URL process. It is a flowchart which shows one Example of a blog display process.

Explanation of symbols

BS ... Blog server, MS ... Music distribution server, AS ... Affiliate program site, DB1 ... Blog entry database, DB2 ... Playlist entry database, Ua ... User system (blog creation client device), Ub, Uc ... General user system , PL ... portable music player, PP ... music player software, D ... music storage, R ... playback history storage means, WB ... WWW browser, X ... communication network

Claims (5)

A client device for creating a blog that edits a predetermined blog site managed by a blog server interconnected so as to be communicable via a communication network,
Entry input means for inputting a blog entry to be reflected on the blog site;
Storage means for storing entry information for registering the input blog entry to the blog server;
A plurality of contents are stored, and any one of the contents is reproduced individually or sequentially according to an instruction from the user, and predetermined identification information corresponding to the reproduced contents is reproduced along with the date and time when the contents are reproduced. Acquisition means for acquiring the accumulated reproduction history information from a predetermined content reproduction unit that accumulates as information;
Generating means for generating one history entry information including at least a reproduction date and a list of contents reproduced on the reproduction date based on the acquired reproduction history information for each date of the reproduction date ;
A blog creation client device comprising registration means for registering the generated history entry information in the blog server based on the stored entry information regardless of whether or not the blog entry is input. Means for intercommunication with a blog creation client device via a communication network;
A blog entry record corresponding to each of a plurality of blog creators, each record including a blog entry input by a user is stored so as to be identifiable by identification information previously given to each blog creator. 1 storage means;
A playlist entry record corresponding to each of a plurality of blog creators, each record including history entry information including at least a playback date and a list of contents played back on the playback date, for each date of the playback date. A second storage means for accumulating identifiable by identification information given in advance for each blog creator;
Means for receiving a blog entry request including a blog entry together with the identification information from the connected blog creation client device;
Means for storing the received blog entry in a blog entry record corresponding to the received identification information from among those stored in the first storage means in response to receiving the blog entry request;
Means for receiving a playlist entry request including history entry information together with the identification information from the connected blog creation client device;
Means for storing the received history entry information in a playlist entry record corresponding to the identification information stored in the second storage means in response to reception of the playlist entry request;
Means for receiving a blog browsing request for browsing a blog site corresponding to predetermined identification information from the connected blog creation client device;
In response to receiving the received blog browse request, the blog entry record of the corresponding identification information is read from the first storage means, and the playlist entry record of the corresponding identification information is read from the second storage means When,
A blog server comprising means for returning a combination of the read blog entry record and the playlist entry record to the connected blog creation client device as a response to the blog browse request. Blog server according to claim 2, characterized in that for each of the contents in a contents list to be displayed on the blog site based on the reproduction list entry record, further comprising means for setting a hyperlink to the affiliate program site . On the computer,
A procedure for inputting a blog entry to be reflected in a predetermined blog site managed by a blog server that is interconnected so as to be able to communicate via a communication network;
Storing entry information for registering the input blog entry to the blog server;
A plurality of contents are stored, and any one of the contents is reproduced individually or sequentially according to an instruction from the user, and predetermined identification information corresponding to the reproduced contents is reproduced along with the date and time when the contents are reproduced. A procedure for acquiring the accumulated reproduction history information from a predetermined content reproduction unit that accumulates as information;
Generating one history entry information including at least a reproduction date and a list of contents reproduced on the reproduction date based on the acquired reproduction history information for each date of the reproduction date ;
A program for executing the procedure for registering the generated history entry information in the blog server based on the stored entry information regardless of whether or not the blog entry is input. On the computer,
A procedure for interconnecting with a blog creation client device via a communication network,
A blog entry record corresponding to each of a plurality of blog creators, each record including a blog entry input by the user, so that identification information preliminarily assigned to each blog creator can be identified. A procedure for accumulating in one storage means;
A playlist entry record corresponding to each of a plurality of blog creators, each record including history entry information including at least a playback date and a list of contents played back on the playback date, for each date of the playback date. , A procedure for accumulating in a predetermined second storage means so as to be identifiable by identification information given in advance for each blog creator,
A procedure for receiving a blog entry request including a blog entry together with the identification information from the connected blog creation client device;
In response to receiving the blog entry request, a procedure for storing the received blog entry in a blog entry record corresponding to the received identification information from among those stored in the first storage means;
A procedure for receiving a playlist entry request including history entry information together with the identification information from the connected blog creation client device;
A procedure for accumulating the received history entry information in a playlist entry record corresponding to the identification information stored in the second storage means in response to reception of the playlist entry request;
A procedure for receiving a blog browsing request for browsing a blog site corresponding to predetermined identification information from the connected blog creation client device;
In response to receiving the received blog browse request, the blog entry record of the corresponding identification information is read from the first storage means, and the playlist entry record of the corresponding identification information is read from the second storage means When,
A program for executing a procedure for returning a combination of the read blog entry record and a playlist entry record to the connected blog creation client device as a response to the blog browse request.

Images