JP5321863B2 - Content cache device, content cache method, and computer program - Google Patents

Description

  Embodiments described herein relate generally to a content cache device, a content cache method, and a computer program.

  There is known a content synthesizing apparatus that synthesizes contents obtained by combining a plurality of pieces of information (Web resources) on the Internet and allows a user to view the synthesized contents as a program. It is assumed that there are images, texts, voices, moving images, etc. on the Internet, and that the original content is synthesized by a user's terminal based on the design drawing. At this time, this blueprint is called a scenario.

There are cases where the user views the content once viewed on the terminal again. When a user wants to watch a program once viewed on a terminal owned by the user, it is necessary to store information somewhere. The following three cases are generally considered as places for storing information.
(1) Terminal owned by the user (2) Another terminal owned by the user (3) Server

  A portable terminal can be considered as a terminal owned by the user (1). In this case, since it is considered that the capacity that the terminal can hold is small, it is difficult to think about holding information in the terminal held by the user.

  As another terminal owned by the user (2), for example, a television or home server in the home, a server on the network owned by the user, or the like can be considered. However, these are not necessarily held by the user.

  When the server providing the service (3) holds information, it is necessary to provide the same service to many users. Therefore, the amount of information stored by each person is accumulated, and a large amount of information is held. In order to solve this problem, as a conventional technique, a method of sharing the same data among different users has been proposed. However, with this method, at least one piece of information needs to be held near the user, such as at home or a shared server.

Japanese Patent Laid-Open No. 2001-159998 JP 2004-166189 A

  The present invention provides a content cache device, a content cache method, and a computer program that can re-view a previously viewed program while reducing the amount of information to be held.

  A content cache device as an embodiment of the present invention includes a BM storage instruction receiving unit, a bookmark history holding unit, a first acquisition unit, a cache holding unit, a holding determination unit, a reproduction instruction receiving unit, and a second acquisition unit. And a mashup unit and an output unit.

  The BM storage instruction receiving unit receives a bookmark instruction for a scenario that defines a method for combining a plurality of resources each having an identifier.

  The bookmark history holding unit stores the scenario in which the bookmark instruction is given in association with the reception time information of the bookmark instruction in the BM storage instruction receiving unit.

  The first acquisition unit acquires the resource defined in the scenario from a location corresponding to the identifier of the resource.

  The cache holding unit stores a resource, an identifier of the resource, and reception time information in association with each other.

  The holding determination unit, when a resource having the same identifier and the same configuration as the resource acquired by the first acquisition unit is present in the cache holding unit, the resource, the identifier of the resource, and the reception time information When it is deleted from the cache holding unit and does not exist, the acquired resource, the identifier of the acquired resource, and the reception time information of the bookmark instruction are associated with each other and stored in the cache holding unit.

  The reproduction instruction receiving unit accepts a reproduction instruction of a first scenario that is one of the scenarios held in the bookmark history holding unit.

  The second acquisition unit, when the resource identifier specified in the first scenario exists in the cache holding unit, according to the reception time information associated with the first scenario and the resource identifier, The resource is acquired from the cache holding unit, and when the resource does not exist, the resource is acquired from a location corresponding to the identifier.

  The mashup unit generates a program by synthesizing the resources acquired by the second acquisition unit in response to a reproduction instruction of the first scenario.

  The output unit outputs the program.

1 shows a configuration of a Web resource cache device as a content cache device according to the present embodiment. The operation of the device in FIG. 1 when instructed to save BM from the terminal is shown. The operation flow of holding judgment is shown. The operation of this device when BM history is requested is shown. The operation of this device when instructed to play BM is shown. An example of BM history data held by the BM history holding unit is shown. The example of the data which a cache holding part has is shown.

  An outline of the present embodiment will be described. In this embodiment, a user's terminal acquires and processes a plurality of Web resources such as images, texts, sounds, and videos existing on the Web based on a certain design drawing, and presents them to the user as a set of contents. Assumes that. At this time, acquiring and processing Web resources is called mashup, and the design drawing that instructs mashup is called a scenario. The content created by mashup is called a “program”. Like TV broadcast programs, programs are not only those that continuously display text, images, audio, video, etc., but those that only display text, only images, only audio, those that read text, video automatically Various types of content can be considered, such as those that wait for user input as well as change.

  When using such a terminal, the user may want to view a program once viewed again. Here, a set of scenarios and web resources to be stored for viewing again is defined as a bookmark (BM). In addition to scenarios, BM is a collection of web resources that are used in programs such as images, text, audio, and video, or that are required during the mashup process. There is a difference that a Web resource is a single piece of information identified by a URI, and a BM is a collection of scenarios and single or multiple Web resources required for program playback.

  In the configuration in which Web resources on the Internet assumed in the present embodiment are synthesized and presented by a terminal held by the user, the original Web content exists on the Internet. Thus, if the user wants to watch the program again, the original web resource may still exist on the Internet, or may no longer exist (disappear or change). obtain.

  In this embodiment, for information that is determined to be likely to disappear or change from the Internet, the information is cached in a content cache device (Web resource cache device), and the cached information is stored at the time of re-viewing. Use.

  On the other hand, for a Web resource that is determined to be highly likely to remain on the Internet in the future, the information is not stored in the content cache device but is acquired again from the Internet at the time of viewing again. In other words, the user does not need to hold the original Web resource, and if the user wants to watch the program again, it can be acquired from the Internet again.

  As described above, the amount of information that the user's terminal or server should hold can be reduced, and the possibility that the BM cannot be reproduced due to the absence of necessary Web resources can be reduced.

  Hereinafter, this embodiment will be described in detail.

  FIG. 1 shows a configuration of a Web resource cache device 101 as a content cache device according to the present embodiment.

  1 includes a BM storage instruction receiving unit 102, a scenario holding unit 103, a BM history holding unit 104, a mashup unit 105, an acquisition unit (first acquisition unit, second acquisition unit) 106, and a cache holding unit 107. , Holding determination unit 108 and request receiving unit (reproduction instruction receiving unit, output unit) 109. The first acquisition unit acquires the Web resource at the time of BM save instruction (described later), and the second acquisition unit refers to the function of acquiring the Web resource during scenario playback. However, the first acquisition unit and the second acquisition unit are physically the same. It may be a separate device or a separate device.

  The BM storage instruction receiving unit 102 is configured to be able to communicate with the terminal A wirelessly or by wire. The request receiving unit 109 is configured to be able to communicate with the terminal B by wireless or wired communication. The acquisition unit 106 is configured to be able to communicate with a plurality of servers 201 via a network 301 such as the Internet. Terminal A is a terminal for instructing a bookmark of a scenario, and is operated by a user. The terminal B is a terminal that instructs the scenario reproduction, and is operated by the user. The terminal B may be the same device as the terminal A or may be a different device. This content cache device may be arranged as a server in the user's home or on the Internet.

  Hereinafter, the function of each block provided in the present apparatus and the overall operation will be described with reference to the flowcharts of FIGS.

  FIG. 2 shows the operation when this device is instructed to save BM from terminal A.

  The BM storage instruction receiving unit 102 receives the BM storage instruction sent from the terminal A owned by the user (step S11). In this BM save instruction, an identifier (scenario identifier) for identifying a scenario is stored.

  An identifier consists of a character string such as a URI or a numerical value. The scenario specifies a resource (URI, etc.) of a plurality of Web resources, and defines a synthesis method (reproduction method) of the plurality of Web resources.

  The terminal A may issue a BM save instruction for the scenario during playback of the scenario, or may select a scenario from a list of scenarios played back in the past and give a BM save instruction. Alternatively, the scenario may be specified by other methods and the BM save instruction may be issued.

  The BM storage instruction receiving unit 102 requests a scenario from the scenario storage unit 103 based on the scenario identifier stored in the BM storage instruction, and acquires the scenario from the scenario storage unit 103 (step S12).

  In the present embodiment, the scenario holding unit 103 is provided in the present apparatus, but may be in a place where the apparatus is wired or wirelessly connected or on the Internet 301. Further, a predetermined number of scenarios may be stored in the BM storage instruction receiving unit 102 in advance to reduce the time required for scenario acquisition.

  The BM storage instruction receiving unit 102 sends a BM storage instruction including the identifier (user identifier) of the user who instructed the BM storage, the scenario identifier, and the reception time information of the BM storage instruction to the BM history storage unit 104 ( Step S13). The reception time information represents the time when the BM storage instruction is issued (BM storage instruction time), that is, the time when the BM storage instruction is received. The user identifier may be acquired at the same time as the BM storage instruction, or may be acquired during a separate authentication procedure when performing user authentication.

  Receiving the BM storage instruction, the BM history holding unit 104 stores the user identifier, the scenario identifier, and the BM storage instruction time as one set and stores it as a BM history.

  FIG. 6 shows an example of BM history data held by the BM history holding unit 104.

  The BM history holding unit 104 can hold a certain amount of BM history. In the illustrated example, the BM history includes the number of playbacks. The number of times of reproduction is the number of times of reproduction of a scenario reproduced according to a reproduction instruction from terminal B described later. The illustrated time includes year, date, hour, minute, and second, but it is not necessary to include all of them. For example, the year may be omitted.

  The BM history holding unit 104 may delete the corresponding data when a certain time has elapsed after receiving the BM storage instruction or when receiving an instruction from the user. Moreover, when the capacity (storage capacity) that can be held is exceeded, a part of the data may be erased. The data to be deleted may be determined based on, for example, the number of scenario playbacks, the ratio of the number of playbacks between scenarios in each scenario, or the BM save instruction time. Alternatively, it can be determined at random. Data for which the user has instructed to save and data whose number of reproductions is equal to or greater than a certain value may be excluded from being erased.

  The BM storage instruction receiving unit 102 sends the scenario acquired from the scenario holding unit 103 and the reception time information (BM storage instruction time) to the mashup unit 105 (step S14).

  Based on the scenario sent from the BM storage instruction receiving unit 102, the mashup unit 105 identifies a Web resource necessary for mashup of the scenario (step S15). The mashup unit 105 sends the acquisition instruction information instructing acquisition of the required Web resource, that is, the Web resource specified in the scenario, to the acquisition unit 106 (step S16). The acquisition instruction information includes an identifier (in this case, a URI) of a Web resource instructing acquisition, a BM storage instruction time, and the like.

  The acquisition unit 106 tries to acquire the Web resource instructed from the mashup unit 105 from the Web resource holding server 201 on the Internet 301 based on the identifier of the Web resource (Step S17).

  For Web resources that could not be acquired from the Web resource holding server 201, a cache acquisition request is sent to the cache holding unit 107 (step S20). The cache holding unit 107 sends the corresponding cached Web resource (for example, the Web resource having the same identifier and associated with the same or the latest BM storage instruction time) to the acquisition unit 106 (Step S21).

  For a Web resource that cannot be acquired from the outside and that does not have a cache in the cache holding unit 107, a message indicating that the Web resource has not been acquired is returned to the mashup unit 105. In this case, the mashup unit 105 may present to the user that the Web resource has not been acquired.

  In steps S20 and S21, if a Web resource cannot be acquired from the Web resource holding server 201, an attempt is made to acquire a cache from the cache holding unit 107. However, this process is not essential and can be omitted. It is. In this case, it may be returned to the mashup unit 105 that the information could not be acquired.

  The acquisition unit 106 sends the Web resource acquired from the Web resource holding server 201 and the acquisition instruction information (BM storage instruction time, Web resource identifier, etc.) acquired from the mashup unit 105 to the holding determination unit 108 as a set. (Step S19).

  At this time, the acquisition unit 106 may calculate the hash value of the acquired Web resource and send the hash value to the holding determination unit 108. By sending the hash value of the Web resource, as described later, even if the Web resource has the same identifier, it can be detected at high speed that the content of the Web resource has changed.

  The holding determination unit 108 determines whether to cache the acquired Web resource based on the data sent from the acquisition unit 106 (step S22).

  When the holding determination unit 108 determines to hold, the Web resource, its identifier, and the BM storage instruction time are sent to the cache holding unit 107 (step S23), and the cache holding unit 107 sends the received Web resource, Web resource identifier and The BM storage instruction time is held (step S24). At this time, the hash value may also be sent to the cache holding unit 107 and the hash value may be held in the cache holding unit 107.

  FIG. 7 shows an example of data that the cache holding unit 107 has. One row corresponds to one record. In this example, a Web resource identifier, a BM storage instruction time, Web resource data (bits), and a Web resource hash value are stored. It means that resources having the same hash value have the same configuration (data). A Web resource held in the cache holding unit 107 may be simply referred to as a cache. Even Web resources with the same identifier can be stored separately if the BM save instruction time is different. As a result, Web resources at a specific time in the past can be obtained. Note that a scenario ID may be added to the cache holding unit 107 in order to identify a scenario using the Web resource and make a determination according to the scenario, such as a reproduction frequency.

  The cache holding unit 107 may delete the corresponding data (record) when a predetermined time has elapsed since the holding. There is also a method of deleting the cache with a certain probability. In this case, this probability may change dynamically depending on the user's setting, program content, BM playback rate, and BM playback count. Web resources that do not interfere with BM playback may be deleted preferentially. When the scenario is deleted by the BM history holding unit 104, the cache holding unit 107 uses resources that are used in the deleted scenario and are not used in other scenarios held by the BM history holding unit 104. It may be erased.

  When the holding determination unit 108 determines not to hold, the holding determination unit 108 instructs the cache holding unit 107 to delete the cache (step S25), and the cache holding unit 107 includes the cache and the Web resource identifier associated therewith, The BM storage instruction time, hash value, etc. are deleted (step S26). The timing of the instruction to delete the cache may be a point in time when it is determined not to hold it, or may be another time later in order to reduce the processing load.

  Hereinafter, the holding determination process performed in step S22 will be described in more detail.

  FIG. 3 shows an operation flow for holding determination.

  The holding determination unit 108 receives the web resource (the hash value if a hash value has been sent), the web resource identifier, and the BM storage instruction time included in the acquisition instruction information from the acquisition unit 106 (step S31).

  The holding determination unit 108 determines whether a resource having the same identifier as the Web resource has been requested in the past (S32). This is done by confirming whether or not the same identifier as the Web resource is held in the cache holding unit.

  When it is determined that the request has not been made until now, it is determined to hold the Web resource in the cache holding unit 107 (step S34). The cache holding unit 107 holds the Web resource together with its identifier, BM storage instruction time, and hash value.

  If a resource with the same identifier as the Web resource has been requested in the past, the following check is performed.

  It is determined whether or not the configuration of the Web resource (cache) with the same identifier held in the cache holding unit 107 is different from the acquired Web resource (step S33). That is, it is determined whether the data (bits) of both Web resources match. When the hash value of the Web resource is sent from the acquisition unit 106, instead of comparing the data, the sent hash value is compared with the cached hash value so that a high-speed determination can be made. Is possible.

  If it is determined in step S33 that the acquired web resource and the stored web resource (cache) have different configurations, it is determined that the acquired web resource is held in the cache holding unit 107 (step S34). ). The cache holding unit 107 holds the Web resource together with its identifier, BM storage instruction time, and hash value.

  When the acquired Web resource and the stored Web resource (cache) configuration match each other, the BM storage instruction time of the cache is checked (step S35).

  When the cache storage time is after a certain time before the target BM storage instruction time (BM storage instruction time sent from the acquisition unit 106), that is, the target BM storage instruction time If the time difference from the cache BM storage instruction time is less than the threshold, the cache and its associated data are deleted and it is determined not to retain the acquired Web resource (step S36).

  Here, the fixed time refers to a relatively long period such as one month. If acquisition of the Web resource is instructed multiple times and the Web resource obtained from the Web resource holding server has not changed in the meantime, if the interval is short, the interval until the next acquisition instruction is short, In addition, since it can be estimated that the Web resources are not different (that is, the same), it is determined that the cache may be deleted.

  On the other hand, when the cache BM instruction save time is earlier in time than a certain time before the target BM save instruction time, that is, the target BM save instruction time and the cache BM save instruction time If the time difference is greater than or equal to the threshold value, it is determined that the cache is retained as it is and the acquired Web resource is not retained (step S34). This is called the first method. At this time, as an alternative method, the BM instruction storage time of the cache may be updated to the target BM storage instruction time (second method). Alternatively, only the obtained BM storage instruction time and the Web resource identifier to be acquired may be stored in the cache holding unit 107, and the data body (bit) of the Web resource may be referred to the cache (first) 3 method). In the case of the third method, a field for referring to the ID of the record to be referred to may be added to the table of the cache holding unit.

  The first method and the second method are effective when it is desired to suppress the capacity of the cache holding unit as much as possible. After the content (configuration) of a resource on the Internet changes, the resource does not return to its original content (or the possibility is very low). When playing back a scenario at the BM save instruction time, the possibility of playing the same content as at the time of the instruction can be greatly increased. The third method is a method that increases the capacity of the cache holding unit 107 slightly compared to the first and second methods, but enables more reliable reproduction.

  The description given above with reference to FIG. 2 is the operation when instructed to save BM. The operation when performing BM playback is described below. When performing BM playback, the terminal that wants to play back the BM (hereinafter referred to as terminal B) acquires the BMM history (BM list) from this device and specifies the BM to play back.

  Fig. 4 shows the operation of this device when a BM history is requested.

  FIG. 5 shows the operation of this apparatus when instructed to perform BM playback.

  In FIG. 4, the terminal that wants to reproduce the BM (hereinafter, terminal B) first sends a request for browsing the BM history to the request receiving unit 109 (step S41). Note that the playback terminal B may be the same as or different from the terminal A that issued the BM storage instruction. This makes it possible, for example, to BM content that has been viewed from a mobile terminal when going out, and to continue to enjoy high-definition information on a large-screen TV after returning home or once again.

  The request receiving unit 109 sends a BM history acquisition request to the BM history holding unit 104 (step S42).

  The BM history holding unit 104 passes the BM history to the request receiving unit 109 (step S43). The BM history includes multiple BMs.

  The request receiving unit 109 passes the BM history to the terminal B (Step S44). The terminal B presents this BM history to the user, thereby causing the user to select which BM is to be played back, that is, which scenario is to be played back. The scenario selected for playback corresponds to the first scenario.

  In FIG. 5, when a BM to be played is instructed by the user, the terminal B sends a BM playback instruction to the request receiving unit 109 (step S51).

  Upon receiving the reproduction request, the request receiving unit 109 sends the designated BM reception time information (BM storage instruction time) and the scenario to the mashup unit 105 (step S52).

  The mashup unit 105 mashes up the scenario. First, a Web resource necessary for mashup specified in a scenario is specified (step S53), and an acquisition request for the specified Web resource is sent to the acquisition unit 106 (step S54). The acquisition request includes the BM storage instruction time and the identifier of the Web resource to be acquired.

  The acquisition unit 106 sends a cache acquisition request to the cache holding unit 107 based on the BM storage instruction time and the Web resource identifier (step S55). The cache acquisition request includes the BM storage instruction time and the Web resource identifier.

  The cache holding unit 107 checks whether there is a cache (Web resource) associated with the same identifier as that of the Web resource and with the same time as the BM storage instruction time (Step S56). If it exists, the cache is returned to the acquisition unit 106, and the acquisition unit 106 further sends the cache to the mashup unit 105 (step S57).

  At this time, if the first method is used in step S34 of FIG. 3, the following processing may be performed when it is determined in step S56 that there is no cache. That is, it is checked whether or not there is a cache associated with the same identifier as the identifier of the Web resource. If there is, a past cache closest to the BM storage instruction time is returned to the acquisition unit 106. As a first method, of the two Web resources determined to have the same configuration in step S33 in FIG. 3, the one that originally existed in the cache holding unit 107 is left as it is, and the other (Web resource holding) This is because the Web resource acquired from the server 201 is deleted. As described above, this first method is effective in a situation in which after a content (configuration) of a resource on the Internet changes, the resource is unlikely to return to the original content. However, even if the original contents are restored, there is no problem in operation. If the assumption is made that there is no possibility of returning to the original contents, and the first method is adopted, the determination in step S33 in FIG. 3 shows that multiple Web resources (caches) with the same identifier are held in cache. When present in the unit 107, it may be compared whether or not it is the same as only the Web resource closest in time from the target BM storage instruction time.

  Similar considerations apply when the second method is used in step S34 in FIG. 3, and if it is determined in step S56 that there is no cache, a cache associated with the same identifier as that of the Web resource exists. In this case, the future cache closest to the BM storage instruction time may be returned to the acquisition unit 106.

  On the other hand, if the corresponding cache does not exist, the cache holding unit 107 returns that fact to the acquisition unit 106, and the acquisition unit 106 acquires the Web resource from the Web resource holding server 201 based on the identifier of the Web resource. Try (S58). Note that the Web resource has been acquired at least once when the BM save instruction is issued (see step S17 in FIG. 2). Therefore, when there is no cache, the holding judgment unit 108 needs to hold the cache. This indicates that the resource is determined not to exist (see steps S22 and S25 in FIG. 2).

  When the acquisition unit 106 cannot acquire the Web resource, that is, when the Web resource does not exist on the Internet 301, the acquisition unit 106 notifies the mashup unit 105 to that effect (S58, S59).

  When the Web resource can be acquired, the acquiring unit 106 sends the acquired Web resource to the mashup unit 105 (S58, S60).

  The mashup unit 105 uses the Web resource acquired from the acquisition unit 106 to complete the scenario mashup, and returns the mashup result program to the request reception unit 109 (step S61). If there are Web resources that could not be acquired, appropriate resources may be placed in that part. Appropriate resources may be stored in advance in the apparatus, or may be acquired from a server on the network by an arbitrary method. For example, similar information may be searched and used, or alternative contents such as advertisements may be used.

  The request receiving unit 109 sends the program passed from the mashup unit 105 to the terminal B (step S62).

  Terminal B displays the program received from request reception unit 109 (step S63). As a result, the scenario at the time when the BM save instruction is given can be played back on terminal B.

  As described above, according to the present embodiment, among the Web resources defined in the scenario for which the BM instruction is given, the Web resource that is determined to be obtainable from the network at the time of the subsequent re-viewing is not retained by this apparatus. As a result, the amount of information to be retained can be further reduced as compared with the conventional case.

  In this method, if the Web resource that the retention determination unit 108 determines not to hold is deleted or changed on the Internet, the Web resource cannot be acquired, and the scenario in which the BM save instruction is issued. The same program cannot be synthesized. However, this embodiment reduces the cache holding capacity by allowing this risk to some extent, and is considered to contribute greatly to the reduction of the holding capacity of the cache device.

  In this embodiment, the Web resource is stored in a server on the Internet. However, the Web resource may be in the same terminal, on a home network, or on a LAN. In addition, although the URI of the Web resource identifier is assumed, it may be other file path or IP address.

  Note that the Web resource cache apparatus described in the above embodiment can also be realized by using, for example, a general-purpose computer apparatus as basic hardware. That is, each element in the device can be realized by causing a processor mounted on the computer device to execute a program. At this time, this apparatus may be realized by installing the above program in a computer device in advance, or may be stored in a storage medium such as a CD-ROM or distributed through the network. The program may be implemented by appropriately installing it in a computer device. In addition, the holding units 103, 104, and 107 in the apparatus include a memory, a hard disk or a storage medium such as a CD-R, a CD-RW, a DVD-RAM, a DVD-R, or the like that is built in or externally attached to the computer apparatus. Can be realized by appropriately using.

  Further, the present invention is not limited to the above-described embodiments as they are, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. In addition, various inventions can be formed by appropriately combining a plurality of components disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, constituent elements over different embodiments may be appropriately combined.

Claims (15)

A BM storage instruction receiving unit that receives a bookmark instruction of a scenario associated with a plurality of resources each associated with an identifier;
A bookmark history holding unit for storing the scenario and first reception time information related to the time when the bookmark instruction is received;
A first acquisition unit configured to acquire the resource related to the scenario from a location corresponding to the identifier related to the resource;
A cache holding unit for storing a resource, a corresponding identifier, and second reception time information related to the time at which the resource is stored;
For the acquired resource, determine whether a pre-stored resource having the same identifier as the acquired resource exists in the cache holding unit;
When the pre-stored resource exists, the pre-stored resource from the cache holding unit, an identifier associated with the pre-stored resource, and the pre-stored resource Delete the second reception time information related to the resource,
When the pre-stored resource does not exist, the cache holding unit stores the acquired resource and an identifier related to the acquired resource, and the acquired from the bookmark history holding unit Storing the first reception time information related to the resource as the second reception time information related to the acquired resource;
An evaluation unit;
One of the scenarios held in the bookmark history holding unit, a reproduction instruction receiving unit that receives a reproduction instruction of a first scenario associated with a plurality of resources each associated with an identifier;
For an identifier associated with the first scenario, determine whether an identifier associated with the first scenario exists in the cache holding unit,
When an identifier associated with the first scenario exists in the cache holding unit, a resource corresponding to the identifier is acquired from the cache holding unit,
When an identifier associated with the first scenario does not exist in the cache holding unit, a resource associated with the first scenario is obtained from a location associated with the identifier; a second obtaining unit;
A mashup unit that generates a program by synthesizing the resources acquired by the second acquisition unit according to the reproduction instruction of the first scenario,
An output unit for outputting the program;
A content cache apparatus comprising: The evaluation unit is
Second reception time information associated with the pre-stored resource determined to exist in the cache holding unit, and a time corresponding to the time when the bookmark instruction related to the pre-stored resource is received. 1 Decide whether the time difference of reception time information is larger, smaller or the same as the threshold,
When the time difference is smaller than the threshold, the resource stored in advance is deleted from the cache holding unit,
2. The content cache device according to claim 1, wherein the resource stored in advance is not deleted when the time difference is equal to or greater than the threshold value. The bookmark history holding unit
For each scenario, store the number of playbacks of the scenario that received a playback instruction;
2. The scenario according to claim 1, wherein when the storage capacity of the bookmark history storage unit reaches a certain value, or when an erase instruction is received from a user terminal, the scenario is erased according to the number of times of playback. Content cache device. 2. The content cache device according to claim 1, wherein the bookmark history holding unit deletes a scenario in which a predetermined time has elapsed from the first reception time information for the scenario. Receiving bookmark instructions for scenarios associated with multiple resources each associated with an identifier;
Storing the scenario and first reception time information related to the time when the bookmark instruction is received in a bookmark history holding unit;
Obtaining the resource associated with the scenario from a location corresponding to the identifier associated with the resource;
Based on the cache holding unit that stores the resource, the corresponding identifier, and the second reception time information related to the time when the resource is stored, the same identifier as the acquired resource is acquired for the acquired resource. Determine if another resource with already exists in the cache holding part,
When the another resource exists, the another resource from the cache holding unit, an identifier related to the other resource, and the time related to the time when the other resource is stored in the cache holding unit. Delete the second reception time information related to the resource,
When the another resource does not exist, the cache holding unit stores the acquired resource and an identifier related to the acquired resource, and is related to the acquired resource from the bookmark history holding unit. Storing the first reception time information as second reception time information related to the acquired resource; and
One of the scenarios held in the bookmark history holding unit, receiving a playback instruction for the first scenario associated with a plurality of resources each associated with an identifier; and
For an identifier associated with the first scenario, determine whether an identifier associated with the first scenario exists in the cache holding unit,
When an identifier associated with the first scenario exists in the cache holding unit, a resource corresponding to the identifier is acquired from the cache holding unit,
When an identifier associated with the first scenario does not exist in the cache holding unit, a resource associated with the first scenario is obtained from a location associated with the identifier; and
Generating a program by synthesizing the acquired resources in response to the playback instruction of the first scenario;
An output step of outputting the program;
A content caching method comprising: The time difference between the second reception time information associated with the other resource determined to exist in the cache holding unit and the first reception time information corresponding to the time when the bookmark instruction related to the other resource is received is a threshold value. Determining whether it is larger, smaller or the same;
When the time difference is smaller than the threshold, deleting the another resource from the cache holding unit;
6. The content cache method according to claim 5, further comprising a step of not deleting the another resource when the time difference is equal to or greater than the threshold value. For each scenario, the step of storing the number of times of playback of the scenario for which a playback instruction has been received; 6. The content caching method according to claim 5, further comprising: deleting the scenario according to the number of times.   6. The content caching method according to claim 5, further comprising: deleting a scenario that has passed a predetermined time from the first reception time information for the scenario. Receiving bookmark instructions for scenarios associated with multiple resources each associated with an identifier;
Storing the scenario and first reception time information related to the time when the bookmark instruction is received in a bookmark history holding unit;
Obtaining the resource associated with the scenario from a location corresponding to the identifier associated with the resource;
Based on the cache holding unit that stores the resource, the corresponding identifier, and the second reception time information related to the time when the resource is stored, the same identifier as the acquired resource is acquired for the acquired resource. Determine if another resource with already exists in the cache holding part,
When the another resource exists, the another resource from the cache holding unit, an identifier related to the other resource, and the time related to the time when the other resource is stored in the cache holding unit. Delete the second reception time information related to the resource,
When the another resource does not exist, the cache holding unit stores the acquired resource and an identifier related to the acquired resource, and is related to the acquired resource from the bookmark history holding unit. Storing the first reception time information as second reception time information related to the acquired resource; and
One of the scenarios held in the bookmark history holding unit, receiving a playback instruction for the first scenario associated with a plurality of resources each associated with an identifier; and
For an identifier associated with the first scenario, determine whether an identifier associated with the first scenario exists in the cache holding unit,
When an identifier associated with the first scenario exists in the cache holding unit, a resource corresponding to the identifier is acquired from the cache holding unit,
When an identifier associated with the first scenario does not exist in the cache holding unit, a resource associated with the first scenario is obtained from a location associated with the identifier; and
Generating a program by synthesizing the acquired resources in response to the playback instruction of the first scenario;
An output step of outputting the program;
A computer program for causing a computer to execute. The time difference between the second reception time information associated with the other resource determined to exist in the cache holding unit and the first reception time information corresponding to the time when the bookmark instruction related to the other resource is received is a threshold value. Determining whether it is larger, smaller or the same;
When the time difference is smaller than the threshold, deleting the another resource from the cache holding unit;
10. The computer program according to claim 9, further causing the computer to execute a step of not deleting the another resource when the time difference is equal to or greater than the threshold. For each scenario, the step of storing the number of times of playback of the scenario for which a playback instruction has been received; 10. The computer program according to claim 9, further causing the computer to execute a step of deleting the scenario according to the number of times. 10. The computer program according to claim 9, further causing the computer to execute a step of deleting a scenario that has passed a predetermined time from the first reception time information for the scenario. A BM storage instruction receiving unit that receives a bookmark instruction of a scenario associated with a plurality of resources each associated with an identifier;
A first acquisition unit configured to acquire the resource related to the scenario from a location corresponding to the identifier related to the resource;
A cache holding unit that associates and stores resources and corresponding identifiers;
For the resource acquired by the first acquisition unit, determine whether a pre-stored resource having the same identifier as the acquired resource exists in the cache holding unit,
When the pre-stored resource exists, the pre-stored resource and the identifier associated with the pre-stored resource are deleted from the cache holding unit, and the acquired Do not store the resource and the identifier associated with the acquired resource in the cache holding unit;
An evaluation unit that stores the acquired resource and an identifier associated with the acquired resource in the cache holding unit when the pre-stored resource does not exist;
A content cache device comprising: Receiving bookmark instructions for scenarios associated with multiple resources each associated with an identifier;
Obtaining the resource associated with the scenario from a location corresponding to the identifier associated with the resource;
Based on a cache holding unit that associates and stores a resource and a corresponding identifier, a pre-stored resource having the same identifier as the acquired resource exists in the cache holding unit for the acquired resource. Determine whether
When the pre-stored resource exists, the pre-stored resource and the identifier associated with the pre-stored resource are deleted from the cache holding unit, and the acquired Do not store the resource and the identifier associated with the acquired resource in the cache holding unit;
Storing the acquired resource and an identifier associated with the acquired resource in the cache holding unit when the pre-stored resource does not exist; and
A content caching method comprising: Receiving bookmark instructions for scenarios associated with multiple resources each associated with an identifier;
Obtaining the resource associated with the scenario from a location corresponding to the identifier associated with the resource;
Based on a cache holding unit that associates and stores a resource and a corresponding identifier, a pre-stored resource having the same identifier as the acquired resource exists in the cache holding unit for the acquired resource. Determine whether
When the pre-stored resource exists, the pre-stored resource and the identifier associated with the pre-stored resource are deleted from the cache holding unit, and the acquired Do not store the resource and the identifier associated with the acquired resource in the cache holding unit;
Storing the acquired resource and an identifier associated with the acquired resource in the cache holding unit when the pre-stored resource does not exist; and
A computer program for causing a computer to execute.

Images