Apparatus, systems and methods for providing edge cached media content to media devices based on user history
Summary by NHIP
Edge Cached Media Distribution
The system delivers media content events to devices by identifying secondary units sharing preferred characteristics. It routes requests through distinct communication systems between edge servers and stores user-specified versus hidden events in separate memory portions.
Claim Score by NHIP
Abstract
Systems and methods provide media content events to media devices. An exemplary system receives a request for a media content event from a first media device; communicates the media content event to an edge server communicatively coupled to the first media device based on an identifier of the requesting media device; identifies a second media device based on preferred media content event characteristics associated with the second media device, wherein at least one media content event characteristic of the requested media content event corresponds to at least one of the preferred media content event characteristics of the second media device, and wherein the second media device is able to communicatively couple to the edge server; and in response to identifying the second media device, communicates an identifier of the second media device to the edge server, wherein the requested media content event is communicated to the second media device.

Term
5.5 yearsleft in the term
Expires 10 March 2032, including 52 days of term adjustment.
- Priority and filed
- Granted
- Today
- Expires
20 claims: 3 independent, 17 dependent
- 1Broadest claimClaim Score 16, narrow(NHIP)A method for providing media content events from a media content event access system, the method comprising:receiving, at the media content event access system, a request from a first media device for a media content event, wherein the first media device is a member of a plurality of media devices communicatively coupled to a first edge server, and wherein the plurality of media devices each include a memory with a first portion configured to store content events that are specified by a user and a second portion configured to store other media content events that are hidden from the user;communicating the requested media content event from the media content event access system to the first edge server that is communicatively coupled to the first media device, wherein the media content event access system is communicatively coupled to a second edge server via a first communication system, wherein the second edge server is communicatively coupled to the first edge server via a second communication system that is different from the first communication system, wherein the first media device is identified by a first identifier, and wherein the first edge server communicates the requested media content event to the first media device based on the first identifier;identifying, at the media content event access system, a second media device based on preferred media content event characteristics associated with the second media device, wherein at least one media content event characteristic of the requested media content event corresponds to at least one of the preferred media content event characteristics associated with the second media device, and wherein the second media device is able to communicatively couple to the first edge server and is a member of the plurality of media devices;and in response to identifying the second media device, communicating an identifier of the second media device from the media content event access system to the first edge server, wherein the requested media content event is also communicated to the identified second media device from the first edge server in response to the first edge server receiving the identifier of the second media device from the media content event access system, and wherein the requested media content event is stored in the second portion of the memory of the receiving second media device.
- 10A media device, wherein the media device is identified by an identifier that uniquely identifies the media device from a plurality of other media devices, the media device comprising:a media content stream interface operable to receive a broadcasted media content signal, wherein the broadcasted media content signal comprises a plurality of currently presentable media content events;an edge server interface operable to communicatively couple a first edge server, wherein the first edge server is communicatively coupled to a second edge server via a communication link of a private data transport system, and wherein a media content event access system is communicatively coupled to the second edge server via a communication system that is different from the private data transport system;a storage medium operable to store a plurality of media content events received at the media content stream interface and the edge server interface, wherein the storage medium is defined by a first portion configured to store a first type of media content events that are specified by a user and a second portion configured to store a second type of media content events that are hidden from the user;and a processor system communicatively coupled to the media content stream interface and the edge server interface, controllably coupled to the storage medium, wherein the processor is configured to: establish a communication link via the edge server interface to the first edge server in response to a request from the first edge server;receive a media content event requested by another media device that is receiving the requested media content event from the first edge server, wherein the media content event access system predicts that the user of the media device will want to access the requested media content event, wherein the media content event access system communicates the identifier of the media device to the first edge server, and wherein the requested media content event is communicated to the media device in response to the first edge server receiving the identifier of the media device;store the requested media content event in the second portion of the storage medium that is hidden from the user;and generate information presentable to the user that identifies media content events stored in the first portion of the storage medium, wherein information identifying other media content events stored in the second portion of the storage medium is not presentable to the user, wherein in response to a request from the user to access the requested media content event stored in the second portion of the storage medium, authorization from the media content event access system is received from the edge server to access the requested media content event from the second portion of the storage medium, and wherein the requested media content event is accessed from the second portion pot 4 on of the storage medium so that the requested media content event is presented to the user.
- 16A media content access system that provides media content events to media devices, wherein the media devices have a memory medium with a first portion configured to store a first type media content events that are specified by a user and a second portion configured to store a second type of media content events that are hidden from the user, comprising:a media content storage system that stores a plurality of media content events, wherein one of the stored media content events is a requested media content event that is communicated from a first edge server to a requesting media device that requested the requested media content event;an edge server interface operable to communicatively couple to a second edge server, wherein the second edge server is communicatively coupled to the first edge server via a communication link of a private data transport system;a memory that stores: at least one media content event characteristic for each of the stored media content events;at least one preferred media content event characteristic for each of a plurality of media devices;an identifier for each one of the media devices that uniquely identifies each of the media devices;and user history prediction logic, and a processor system communicatively coupled to the memory, and controllably coupled to the media content storage system and the edge server interface, wherein the processor system is configured to: retrieve an identifier of the requesting media device;identify, from the plurality of media devices, a sub-group of media devices that are capable of establishing a communication link to the first edge server;retrieve content event characteristics associated with the requested media content event;retrieve the preferred media content event characteristic for each of the sub-group of media devices;compare the content event characteristics associated with the requested media content event with the preferred media content event characteristic for each of the sub-group of media devices;identify at least one predicted requesting media device that is likely to request the requested media content event, wherein the preferred media content event characteristic of the predicted requesting media device corresponds to at least one of the content event characteristics associated with the requested media content event;retrieve an identifier of the predicted requesting media device;and communicate the requested media content event, the retrieved identifier of the requesting media device, and the retrieved identifier of the predicted requesting media device to the second edge server, wherein the requested media content event, the retrieved identifier of the requesting media device, and the retrieved identifier of the predicted requesting media device is communicated from the second edge server to the first edge server, wherein the requested media content event is communicated from the first edge server to the requesting media device and wherein the requested media content event is storable in the first portion of the memory medium of the requesting media device, and wherein the requested media content event is communicated from the first edge server to the predicted requesting media device and wherein the requested media content event is stored in the second portion of the memory medium of the predicted requesting media device.
Independent claims3
90 paragraphs in 4 sections, as filed
BACKGROUND
p-0002Media devices, such as a set top box, a stereo, a television, a computer system, a game system, or the like, are often configured to receive media content for presentation to a user viewing and listening to one or more media presentation devices. For example, a set top box (STB) may receive a media content event, such as a movie. After processing, the STB communicates the movie to a television and/or receiver system for presentation to the user.
p-0003Various media content provider systems employ a broadcast-based medium which broadcasts, from a single source, media content to many media devices. For example, a satellite-based media content provider system uplinks media content to a plurality of satellites. The satellites then broadcast the media content down many earth-based antennas which receive the satellite signals. The received satellite signals are processed and communicated to a STB that is communicatively coupled to the antenna. The STB further processes the received satellite signal to generate a signal corresponding to the media content event that is sent to the media presentation devices.
p-0004However, the user of a media device receiving the broadcasted media content is limited to selecting only the currently available broadcast media content. Even though hundreds of channels of different media content may be available, the user may wish to view a media content event that is not being currently broadcast. For example, the user may wish to view a particular movie that is not currently being broadcasted.
p-0005Some STBs are provisioned with a digital video recorder (DVR) that is configured to store a plurality of media content events using a large memory capacity storage medium. In some instances, where the user is aware of a scheduled future broadcast time of the particular media content event of interest, the user may configure their STB to automatically save the particular media content event of interest when it is broadcasted over the media content provider system and is received at the STB.
p-0006In other instances, the media content provider may select one or more media content events of interest which the media content provider believes will likely be of interest to the user. The selected media content events of interest are broadcast to the STB and are automatically saved into the DVR. In some instances, the broadcasting occurs over a secure channel that is not user accessible, and/or is broadcast during off peak usage times, such as late at night. If the user wishes to view one or more of these pre-stored media content events, then the pre-stored media content events are immediately accessible from the STB DVR. Typically, such pre-stored media content events are premium programs or movies available on a pay-per-view basis. Thus, the user must make arrangements with the media content provider to obtain authorization to access the pre-stored media content events of interest.
p-0007In yet another instance, the STB may have a backchannel connection that provides a communication link back to a remote media content access device. Once the user has made arrangements with the media content provider for authorized access to a particular media content event of interest, the selected media content event of interest is communicated from the remote media content access device to the STB via the established communication link. An example backchannel is an Internet connection which is configured to connect the STB to the Internet. The media content access device may be an internet site or the like. Accordingly, the selected media content event of interest is sent from the media content access device to the STB via the Internet.
p-0008However, media content events of interest may be very data intensive, particularly if the selected media content event of interest is provided in a high definition (HD) format. Due to the amount of data of the selected media content event of interest, due to other traffic over the Internet, and due to other transfer capacity limitations, the selected media content event of interest may not be able to be communicated from the remote media content access device to a particular STB in real time. That is, the user may have to wait some duration for communication of the selected media content event of interest, or for communication of at least a substantial initial portion of the selected media content event of interest, before the user may begin to view the selected media content event of interest. In view of this delay, the user may opt to forgo selecting the particular media content event of interest, and instead, choose to view an immediately available (and likely cost free) different media content event of interest.
p-0009Accordingly, there is a need in the arts to provide systems and methods that are more effective in providing media content events of interest to a user in a timely manner.
SUMMARY
p-0010Systems and methods operable to provide media content events to media devices are disclosed. An exemplary embodiment receives, at a media content event access system, a request from a first media device for a media content event; communicates the requested media content event from the media content event access system to an edge server that is communicatively coupled to the first media device, wherein the first media device is identified by a first identifier, and wherein the edge server communicates the requested media content event to the first media device based on the first identifier; identifies a second media device based on preferred media content event characteristics associated with the second media device, wherein at least one media content event characteristic of the requested media content event corresponds to at least one of the preferred media content event characteristics associated with the second media device, and wherein the second media device is able to communicatively couple to the edge server; in response to identifying the second media device, communicates an identifier of the second media device to the edge server; wherein the requested media content event is also communicated to the identified second media device.
BRIEF DESCRIPTION OF THE DRAWINGS
p-0011Preferred and alternative embodiments are described in detail below with reference to the following drawings:
p-0012<figref idrefs="DRAWINGS">FIG. 1</figref> is a block diagram of an embodiment of an automatic content download manager system implemented in communication environment having a plurality of exemplary media devices; and
p-0013<figref idrefs="DRAWINGS">FIG. 2</figref> is a block diagram of an exemplary media device.
DETAILED DESCRIPTION
p-0014<figref idrefs="DRAWINGS">FIG. 1</figref> is a block diagram of an embodiment of an automatic content download manager system <b>100</b> implemented in a communication environment having a plurality of exemplary media devices <b>102</b><i>a</i>-<i>i</i>, generically referred to as a media device <b>102</b>. Examples of media devices <b>102</b><i>a</i>-<i>i </i>may include, but are not limited to, a set top box (STB), storage medium (referred to interchangeably as a digital video recorder (DVR)), a game playing device, a personal computer (PC), a netbook, or the like that are configured to receive media content that is broadcasted from the media content broadcast facility <b>106</b>. The media content may be then presented on a media presentation device <b>107</b>, such as the non-limiting example television (TV). The storage medium may be any storage medium configured to store media content events.
p-0015The media devices <b>102</b> receive broadcasted media content in a broadcasted media content signal communicated via a media content broadcast communication environment <b>104</b>. The media content is broadcast from a media content broadcast facility <b>106</b>. In some systems, the media content broadcast facility <b>106</b> may be referred to as a head end. The media content broadcast facility <b>106</b> is operated by a media content provider. The media content provider controls which particular media content events, and the broadcast times of the media content events, that are broadcasted from the media content broadcast facility <b>106</b>.
p-0016The automatic content download manager system <b>100</b> embodied in the example media devices <b>102</b><i>a</i>-<i>i </i>is further configured to bidirectionally communicate via a communication system <b>108</b>. A portion of the communication system <b>108</b> is preferably a node-based communication system, and may be a private data transport system that transports data (such as media content events) for a fee. Other portions of the communication system <b>108</b> may be a public system, such as the Internet or the like. In some embodiments, the communication system <b>108</b> is a plurality of discrete communication networks interconnected by nodes, such as edge servers. (One skilled in the art appreciates that individual portions of the communication system <b>108</b> are not illustrated.)
p-0017In the example embodiment of <figref idrefs="DRAWINGS">FIG. 1</figref>, a first edge server <b>110</b> is communicatively coupled to each of the media devices <b>102</b><i>a</i>-<i>i </i>via a suitable communication link <b>112</b><i>a</i>-<i>i</i>, generically referred to as a communication link <b>112</b>. A second edge server <b>114</b> is communicatively coupled to the media content event access system <b>116</b> via a suitable communication link <b>118</b>. The communication links <b>112</b> and/or <b>118</b> may be established on an as-needed basis, may be a dedicated communication link, or may be a network of a plurality of cooperatively operating individual communication links.
p-0018The second edge server <b>114</b> is configurable to communicate to the first edge server <b>110</b> via a suitable communication link <b>120</b> established over the communication system <b>108</b>. The communication link <b>120</b> may be established across a plurality of intervening nodes. Alternatively, or additionally, the communication link <b>120</b> may be established external to the communication system <b>108</b>. Further, the communication link <b>120</b> may be a dedicated communication link, or may be a plurality of individual communication links, associated with an edge server communication system. In contrast, the communication links <b>112</b> may be established between the first edge server <b>110</b> and the media devices <b>102</b> via the Internet.
p-0019Embodiments of the automatic content download manager system <b>100</b> are configured to provide a particular media content event to a requesting one of the media devices <b>102</b>. The requested media content event is stored (cached) at the media content event access system <b>116</b>, and is typically not being currently broadcasted from the media content broadcast facility <b>106</b>. Further, the requested media content event has not been stored on the requesting one of the media devices <b>102</b> (since if stored, the media content event could be directly accessed from the user's media device <b>102</b>).
p-0020The request for the requested media content event may be communicated from the requesting media device <b>102</b> to the media content event access system <b>116</b> in any suitable manner. In an example embodiment, the requesting media device <b>102</b> may communicate the request to the media content event access system <b>116</b> over an established Internet-based communication link (not shown). Alternatively, or additionally, the requesting media device <b>102</b> may communicate the request to the media content event access system <b>116</b> over the links <b>112</b>, <b>120</b>, <b>118</b>. Alternatively, or additionally, the requesting media device <b>102</b> may communicate the request to the media content broadcast facility <b>106</b>, or to another remote device and/or third party entity, which then communicates the request to the media content event access system <b>116</b>.
p-0021In response to receiving the request for a particular media content event, the requested media content event is communicated from the media content event access system <b>116</b> to the second edge server <b>114</b>, via the communication link <b>118</b>. Then, the requested media content event is communicated from the second edge server <b>114</b> to the first edge server <b>110</b>, via the communication link <b>120</b>. In some embodiments, the requested media content event is communicated from media content event access system <b>116</b> to the first edge server <b>110</b>.
p-0022The requested media content event is temporarily stored (cached) at the first edge server <b>110</b>. The identifier associated with the requesting media device <b>102</b> is included with, or associated with, the received requested media content event. The identifier uniquely identifies each particular media device <b>120</b> from a plurality of other media devices <b>120</b>, Accordingly, the first edge server <b>110</b> may use the identifier of the requesting media device <b>102</b> to communicate the requested media content event to the requesting media device <b>102</b>. (The requesting media device <b>102</b> is one of the media devices <b>102</b><i>a</i>-<i>i </i>that are linked to the first edge server <b>110</b> via their respective communication link <b>112</b><i>a</i>-<i>i</i>).
p-0023The requested media content event is temporarily stored in the first edge server <b>110</b> for a specified or predefined duration (cached or storage time). After expiration of the storage duration, the requested media content event is erased, over written, or otherwise deleted from the memory of the first edge server <b>110</b> so that the first edge server <b>110</b> may receive and transmit other data to other devices to which it is also linked.
p-0024Embodiments of the automatic content download manager system <b>100</b> are configured to predict which other ones of the non-requesting media devices <b>102</b><i>a</i>-<i>i </i>may be likely to, at a later time, request the same media content event. The prediction is based on an analysis of usage history, and/or a user history, of each of the other ones of the media devices <b>102</b><i>a</i>-<i>i </i>that are, or may be linked, to the first edge server <b>110</b>. If identified as a media device <b>102</b> that is likely to be requesting the requested media content event at some future time, such media devices <b>102</b> are generically referred to herein as a “predicted requesting media device” <b>102</b>. If embodiments of the automatic content download manager system <b>100</b> determine that one or more of the other media devices <b>102</b><i>a</i>-<i>i </i>is a predicted requesting media device <b>102</b>, and therefore will be likely requesting the same media content event at a future time, identifiers of those other media devices <b>102</b><i>a</i>-<i>i </i>(identifiers of the predicted requesting media device <b>102</b>) will be communicated to the first edge server <b>110</b>.
p-0025Based on the received identifiers of the predicted requesting media devices <b>102</b> that are predicted to make a future request for the communicated media content event, the media content event is also sent from the first edge server <b>110</b> to those predicted requesting media devices <b>102</b> for storage. Then, if a user of those predicted requesting media devices <b>102</b> that have stored the media content event decides to request the media content event, the requested media content event is already available from the storage medium of their respective predicted requesting media device <b>102</b>. Accordingly, the requested media content event does not have to be re-transmitted from the media content event access system <b>116</b> to the first edge server <b>110</b>.
p-0026The identifiers of the predicted requesting media devices <b>102</b> may be communicated with the requested media content event to the first edge server <b>104</b>. Alternatively, may be separately communicated to the first edge server <b>104</b>. The identifiers of the requesting media device <b>102</b> and any identified predicted requesting media devices <b>102</b> may be communicated in any suitable manner. In an example embodiment, the identifiers are communicated via the links <b>118</b>, <b>120</b> at the time of communication of the requested media content event to the first edge server <b>110</b>. Alternatively, the identifiers may be included with, or embedded within, the communicated media content event. In other embodiments, the requesting media device <b>102</b> may communicate the identifiers to the first edge server <b>110</b> over an established Internet-based communication link (not shown).
p-0027An unexpected advantage provided by embodiments of the automatic content download manager system <b>100</b> is a cost savings to the media content provider that provides the requested media content event to subscribing media devices <b>102</b><i>a</i>-<i>i</i>. One skilled in the art appreciates that, in a fee based third party edger server system, each time that a media content provider sends a media content event to a requesting one of the media devices <b>102</b><i>a</i>-<i>i</i>, the media content provider must pay a transaction fee to the owner/operators of the communication system <b>108</b>, the first edge server <b>110</b>, and/or the second edge server <b>114</b> for the communication service. When multiple ones of the media devices <b>102</b><i>a</i>-<i>i </i>(the requesting media device <b>102</b> and the predicted requesting media devices <b>102</b>) concurrently receive the same requested media content event from a single transaction, then the media content provider is able to provide the requested media content event to the plurality of media devices <b>102</b><i>a</i>-<i>i </i>using a single communication event that incurs a single transaction fee. Accordingly, the media content provider can avoid subsequent transaction fees when other ones of the media devices <b>102</b><i>a</i>-<i>i </i>(the predicted requesting media devices <b>102</b>) later request the same media content event (since the requested media content event is already available on those predicted requesting media devices <b>102</b>).
p-0028Another unexpected advantage provided by embodiments of the automatic content download manager system <b>100</b> is a bandwidth savings between the media content event access system <b>116</b> and the second edge server <b>114</b>. In the event that different ones of the media devices <b>102</b><i>a</i>-<i>i </i>are concurrently requesting the media content event, and/or are requesting the media content event at different times, the requested media content event need only be sent the one time from the media content event access system <b>116</b> to the second edge server <b>114</b>. Accordingly, bandwidth capacity of the communication link <b>118</b> between the media content event access system <b>116</b> and the second edge server <b>114</b> may be reduced. That is, the bandwidth capacity (defined as the maximum number of bits per second that may be communicated over the communication link <b>118</b>, or bit peak rate) of the communication link <b>118</b> may be less than a corresponding communication link between the media content event access system <b>116</b> and the second edge server <b>114</b> if communication link capacity is otherwise required, on a real time basis, to communicate each and every requested media content event to each and every media device <b>102</b> that is serviced by the media content provider.
p-0029Further, bandwidth utilization of the communication link <b>118</b> between the media content event access system <b>116</b> and the second edge server <b>114</b> may be reduced. That is, bandwidth utilization (defined as the actual number of bits per second being currently communicated over the communication link <b>118</b>) of the communication link <b>118</b> may be less than a corresponding communication link between the media content event access system <b>116</b> and the second edge server <b>114</b> if communication link utilization is otherwise used to communicate, on a real time basis, each and every requested media content event to each and every media device <b>102</b> that is serviced by the media content provider.
p-0030Further, another unexpected advantage provided by embodiments of the automatic content download manager system <b>100</b> is a bandwidth capacity and/or utilization savings over the communication link <b>120</b> established between the first edge server <b>110</b> and the second edge server <b>114</b>. For example, if multiple ones of the media devices <b>102</b><i>a</i>-<i>i </i>are requesting the same media content event at non-coincident times (where the presentation times of the requested media content event are different at each of the requesting media devices <b>102</b><i>a</i>-<i>i</i>), then different portions of the requested media content event must be otherwise streamed across the communication link <b>120</b> at the same time. If the predicted requesting media devices <b>102</b> have previously received and saved the requested media content event during a single communication event, then the different portions of the requested media content event do not need to be concurrently communicated, and/or communicated multiple times, over the communication link <b>120</b>. Accordingly, bandwidth utilization of the communication link <b>120</b> is reduced.
p-0031Further, there may be a memory capacity savings at the first edge server <b>110</b> and/or the second edge server <b>114</b>. The requested media content event (or at least portions thereof) is temporarily stored at the first edge server <b>110</b> and/or second edge server <b>114</b> each time a requested media content event is communicated over the communication system <b>108</b>. Since the requested media content event is communicated to multiple ones of the media devices <b>102</b><i>a</i>-<i>i </i>(the requesting media device <b>102</b> and one or more predicted requesting media devices <b>102</b>) during a single communication event, then memory capacity and/or memory utilization at the first edge server <b>110</b> and/or the second edge server <b>114</b> will be reduced.
p-0032To facilitate disclosure of an exemplary embodiment of the automatic content download manager system <b>100</b>, delivery of media content events to the media devices <b>102</b><i>a</i>-<i>i </i>are briefly described. The media content broadcast facility <b>106</b> receives media content, in the form of a plurality of media content events, from a plurality of local program providers or other content providers (not shown). The provided media content events may include, but are not limited to, a television program, a newscast, a broadcast sports event, a movie, or the like. The media content is typically provided in the form of a video stream and a synchronized audio stream. The media content broadcast facility <b>106</b> processes the received media content streams as necessary to prepare them for transmission to the plurality of media devices <b>102</b><i>a</i>-<i>i</i>. For example, commercials and/or other non-media content event type information may be incorporated with a particular media content event. Further, each media content may be associated with one or more identifiers, such as channel number and/or station call signs. The processed media content events are aggregated together and are broadcast over the media content broadcast system <b>104</b> in one or more media content streams <b>122</b>. The media content streams <b>122</b> are received at each of the media devices <b>102</b><i>a</i>-<i>i. </i>
p-0033A variety of communication system types may be used by the media content broadcast system <b>104</b> to communicate the media content stream <b>122</b>, in a broadcasted media content signal comprising a plurality of currently presentable media content events, to the media devices <b>102</b><i>a</i>-<i>i</i>. The media content broadcast system <b>104</b> may employ a satellite system <b>124</b> wherein an uplink signal <b>126</b> is communicated from a ground antenna <b>128</b> up to one or more satellites <b>130</b>. The exemplary satellite <b>130</b> broadcasts a wireless satellite signal <b>132</b> down to a receiver antenna <b>134</b> that is coupled to a respective one of the media devices <b>102</b><i>a</i>-<i>i</i>. The media devices <b>102</b><i>a</i>-<i>i </i>receive the media content stream <b>122</b> from Their respective receiver antenna <b>134</b>.
p-0034Alternatively, or additionally, the media content broadcast system <b>104</b> may employ an over the air (OTA) system <b>136</b>, wherein the broadcasted media content signal is a wireless signal <b>138</b> that is communicated to the receiver antenna <b>134</b> or to another antenna (not shown). The media devices <b>102</b><i>a</i>-<i>i </i>receive the media content stream <b>122</b> from their respective receiver antenna <b>134</b> or the other antenna.
p-0035Alternatively, or additionally, the media content broadcast system <b>104</b> may employ a cable system <b>140</b>, wherein the broadcasted media content signal is a wire-based signal with the media content stream <b>122</b> that is communicated using a suitable cable <b>142</b> or the like that is coupled to the media devices <b>102</b><i>a</i>-<i>i</i>. Non-limiting examples of the cable <b>142</b> include a fiber optic cable, a coaxial cable, and telephone line.
p-0036In an exemplary embodiment, the media content event access system <b>116</b> comprises a processor system <b>144</b>, a memory <b>146</b>, a media content storage system <b>148</b>, an edge server interface <b>150</b>, and a media content broadcast facility (MCBF) interface <b>152</b>. The processor system <b>144</b> is communicatively coupled to the memory <b>146</b>, and is controllably coupled to the media content storage system <b>148</b>, the edge server interface <b>150</b>, and the media content broadcast facility interface <b>152</b>. The memory <b>146</b> includes memory medium regions that store the user history prediction logic <b>154</b>, media content event (MCE) prediction logic <b>156</b>, and/or a client information database <b>158</b>. The user history prediction logic <b>154</b> and the media content event prediction logic <b>156</b> may be integrated together, and/or may be integrated with other logic, in the various embodiments. Other components not described herein may be included in other embodiments of the media content event access system <b>116</b>. Further, the media content event access system <b>116</b> may be integrated within, or may reside within, the media content broadcast facility <b>106</b>.
p-0037The media content storage system <b>148</b> employs a memory medium that is configured to store a plurality of different media content events, and/or media content events in different formats, such as, but not limited to, a standard definition format and a high definition format. Any number of media content events may be stored in the media content storage system <b>148</b>. Selected media content events may be added to or deleted from the media content storage system <b>148</b> as desired. Preferably, management of the stored media content events is performed by the media content provider. Alternatively, other entities may manage the storage of media content events in the media content storage system <b>148</b>.
p-0038In some embodiments, the media content storage system <b>148</b> is a distributed system that is managed by one or even multiple entities. Memory device components of a distributed media content storage system <b>148</b> may be communicatively coupled together and/or managed using any suitable communication system. In an example embodiment, different memory device components of the media content storage system <b>148</b> are communicatively coupled together via the example communication system <b>108</b>.
p-0039The media content events may be received at the media content event access system <b>116</b> in a variety of manners. For example, media content events may be directly communicated from the media content broadcast facility <b>106</b> to the media content event access system <b>116</b> via an established communication link <b>160</b>. Alternatively, or additionally, the media content event access system <b>116</b> may receive the media content events when broadcasted from the media content broadcast facility <b>106</b> (in a manner similar to that used by the media devices <b>102</b>). Alternatively, or additionally, the media content events may be received on a portable memory medium, such as a compact disc (CD), a flash-type memory, a tape, or the like. Alternatively, or additionally, the media content events may be received from a remote device via the communication system <b>108</b> or another suitable communication system (not shown).
p-0040The memory <b>146</b> and/or the media content storage system <b>148</b> may be any suitable memory device or system. Depending upon the embodiment, the memory <b>146</b> and/or the media content storage system <b>148</b> may be a dedicated memory system, may be part of another component or system, and/or may be a distributed memory system. The memory <b>146</b> and/or the media content storage system <b>148</b> may also include other logic, modules and/or databases not illustrated or described herein. In some embodiments, the memory <b>146</b> and the media content storage system <b>148</b> may be implemented in the same memory medium, device, or system.
p-0041The edge server interface <b>150</b> is configured to communicatively couple the media content event access system <b>116</b> with the example second edge server <b>114</b> via the example communication link <b>118</b>. In some embodiments, the edge server interface <b>150</b> is a generic server interface that may be configured to communicatively couple to a plurality of different second edge servers <b>114</b> that may be geographically dispersed at convenient locations. Further, the edge server interface <b>150</b> may support a plurality of communication links <b>118</b> established with multiple second edge servers <b>114</b>. The communication link <b>118</b> may use any suitable medium and/or system, such as a fiber optic cable, a coaxial cable, a telephone line, a frame relay based system, an internet or intranet system, a local access network (LAN) system, an Ethernet system, a coaxial cable system, a radio frequency (RF) system, a cellular system, or the like. Furthermore, the communication link <b>118</b> may employ a hybrid system comprised of one or more of the above-described mediums and/or systems.
p-0042In practice, the media content broadcast facility interface <b>152</b> is a generic communication interface that is configured to communicatively couple the media content event access system <b>116</b> and the media content broadcast facility <b>106</b> via the communication link <b>160</b>. The communication link <b>160</b> may use any suitable medium and/or system, such as a fiber optic cable, a coaxial cable, a telephone line, a frame relay based system, an internet or intranet system, a local access network (LAN) system, an Ethernet system, a coaxial cable system, a radio frequency (RF) system, a cellular system, or the like. Furthermore, the communication link <b>160</b> may employ a hybrid system comprised of one or more of the above-described mediums and/or systems.
p-0043When the user history prediction logic <b>154</b> is implemented as software, the user history prediction logic <b>154</b> can be stored on any computer-readable medium, such as the memory <b>146</b>, for use by or in connection with any computer and/or processor related system, such as the example processor system <b>144</b>. The memory <b>146</b> is a computer-readable medium that is an electronic, magnetic, optical, or other another physical device or means that contains or stores a computer and/or processor program. The user history prediction logic <b>154</b> can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions associated with the user history prediction logic <b>154</b>. In the context of this disclosure, a “computer-readable medium” can be any means that can store, communicate, propagate, or transport the program associated with the user history prediction logic <b>154</b> for use by or in connection with the instruction execution system, apparatus, and/or device.
p-0044The computer-readable medium of memory <b>146</b> and/or the media content storage system <b>148</b> may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a nonexhaustive list) of the computer-readable medium would include the following: an electrical connection having one or more wires, a portable computer diskette (magnetic, compact flash card, secure digital, or the like), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM, EEPROM, or Flash memory), an optical fiber, and a portable compact disc read-only memory (CDROM). In some embodiments, the computer-readable medium, may be paper or another suitable medium upon which the program associated with the user history prediction logic <b>154</b> is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in memory <b>146</b> or in another memory medium.
p-0045In some embodiments, the communication system <b>108</b> is a content distribution network that provides access to cached data, such as a requested media content event. Edge servers <b>110</b>, <b>114</b>, in a system administration context, are server devices that reside on an “edge” between two networks, typically a private network and the Internet, and is located close to a plurality of client devices (such as the media content event access system <b>116</b> and the media devices <b>102</b><i>a</i>-<i>i</i>). For example, the first edge server <b>104</b> is relatively close to the plurality of media devices <b>102</b><i>a</i>-<i>i</i>. The second edge server <b>114</b> is relatively close to the media content event access system <b>116</b>. A plurality of edge servers, which may include the example edge servers <b>104</b>, <b>114</b>, are communicatively connected with each other and the private network over high capacity communication links. Some embodiments employ Transmission Control Protocol (TCP) and/or User Datagram Protocol (UDP) type connections that may be implemented on backbone network, such as, but not limited to, one or more fiber optic bundles.
p-0046In the various embodiments, the requested media content event is also sent to those predicted requesting media devices <b>102</b> for storage. The predicted requesting media devices <b>102</b> are identified by specifying their identifiers.
p-0047Embodiments of the automatic content download manager system <b>100</b> are configured to identify the predicted requesting media devices <b>102</b> from a large number of media devices <b>102</b><i>a</i>-<i>i</i>. Two criteria are used to identify a media device <b>102</b> as being one of the predicted requesting media devices <b>102</b>.
p-0048A first criteria is a proximity criteria that corresponds to a proximity of a sub-group of the media devices <b>102</b><i>a</i>-<i>i </i>to the first edge server <b>104</b> that is providing the requested media content event to the requesting media device <b>102</b>. That is, the sub-group of the media devices <b>102</b><i>a</i>-<i>i </i>must be able to establish a communication link <b>112</b> to the first edge server <b>104</b> that is providing the requested media content event to the requesting media device <b>102</b>. For those media devices <b>102</b><i>a</i>-<i>i </i>that are unable to establish a communication link <b>112</b> to the first edge server <b>104</b> that is providing the requested media content event to the requesting media device <b>102</b>, such media devices <b>102</b><i>a</i>-<i>i </i>would not be identified as a predicted requesting media device <b>102</b>.
p-0049Information identifying sub-groups of media devices <b>102</b> that are able to establish a communication link <b>112</b> to a particular one of a plurality of first edge servers <b>104</b> is stored in the memory <b>146</b>, such as in the client information database <b>158</b>. The identifiers of the media devices <b>102</b><i>a</i>-<i>i </i>is a particular sub-group of media devices <b>102</b> are associated with the sub-group and are stored in the client information database <b>158</b>. Alternatively, or additionally, one or more of those first edge servers <b>110</b> to which a particular media device <b>102</b> is capable of establishing a link with may be stored with, or associated with, identifiers of each one of the media devices <b>102</b>. Any suitable database format may be used to identify members of a particular sub-group of media devices <b>102</b> by the various embodiments.
p-0050A media device <b>102</b> may be a member of multiple sub-groups of media devices <b>102</b>. In such situations, the automatic content download manager system <b>100</b> also tracks if and/or when a requested media content event is sent to that particular media device <b>102</b> when it has been identified as a predicted requesting media device <b>102</b> or a requesting media device <b>102</b>. Accordingly, the requested media content event is not sent to that particular media device <b>102</b> multiple times.
p-0051A second criteria is a user media content event preference criteria that corresponds to one or more characteristics of available media content events that the user may be interested in receiving at their media device <b>102</b>. Based on a history of user selection of media content events, and/or based on a history of media content events requested by an associated media device <b>102</b>, a plurality of media content event characteristics are identified which correlate to media content events that are likely to be requested by the user of a particular one of the media devices <b>102</b><i>a</i>-<i>i </i>and/or the associated media device <b>102</b>. That is, embodiments of the automatic content download manager system <b>100</b> are configured to learn about the user's media content event selection habits and/or about a media device's <b>102</b> request pattern. Based upon what is learned about a particular user and/or media device <b>102</b>, embodiments are configured to predict whether or not a requested media content event that is communicated to a requesting media device <b>102</b> is also likely to also be requested by the media device <b>102</b> of that particular user.
p-0052In an example embodiment, a history of selected media content events selected by users of each of the media devices <b>102</b><i>a</i>-<i>i </i>serviced by the media content provider may be stored in the client information database <b>158</b> or may be stored in another suitable memory medium. Alternatively, or additionally, a history of selected media content events requested by each of the media devices <b>102</b><i>a</i>-<i>i </i>serviced by the media content provider are stored in the client information database <b>158</b> or may be stored in another suitable memory medium.
p-0053Each media content event is associated with a plurality of media content event characteristics. A non-limiting example of a media content event characteristic includes one or more subject matter themes of the media content event. For example, the media content event may be associated with an action theme, a romance theme, a comedy theme, a travel theme, or the like. Other non-limiting media content event characteristics are identities of actors, identities of directors, identities of producers, identification of film locations, identity of a film production entity, identity of a media content event title (such as for a television series or the like), or the like.
p-0054The processor system <b>144</b>, executing the user history prediction logic <b>154</b>, analyzes the media content event characteristics of a plurality of media content events that have been selected by the user of a particular media device <b>102</b>. The media content event characteristics of selected media content events are used to identify one or more user preferences. The user preferences are defined by identifying those media content event characteristics that are common among the selected media content events.
p-0055For example, but not limited to, the media device <b>102</b><i>a </i>may often present action themed media content events and comedy themed media content events to the users of the media device <b>102</b><i>a</i>. Alternatively, or additionally, a particular media device <b>102</b><i>a </i>may often present media content events with the actor Bob Smith, and/or media content events filmed in a jungle. In contrast, the media device <b>102</b><i>b </i>may often present romantic themed media content events and comedy themed media content events to the users of the media device <b>102</b><i>b</i>. Alternatively, or additionally, a particular media device <b>102</b><i>b </i>may often present media content events with the actor John Doe, and/or media content events filmed in Paris.
p-0056In the above illustrative simplified examples, the automatic content download manager system <b>100</b> would “learn” that the media device <b>102</b><i>a </i>is likely to request media content events that have action themes, have comedy themes, have the actor Bob Smith, and/or that are filmed in the jungle. In contrast, the automatic content download manager system <b>100</b> would “learn” that the media device <b>102</b><i>b </i>is likely to request media content events that have romantic themes, have comedy themes, have the actor John Doe, and/or that are filmed in Paris. The preferred media content event characteristics are determined and stored in the client information database <b>158</b>. Over time, for each of the many media devices <b>102</b><i>a</i>-<i>i</i>, a large number of preferred media content event characteristics may be associated with each particular media device <b>102</b>. The associated preferred media content event characteristics may be based on history of a single user, an identified user, or a group of users, that are associated with a particular media content event.
p-0057When the media content event access system <b>116</b> sends a particular requested media content event to the first edge server <b>104</b> for communication to the requesting media device <b>102</b>, the processors system <b>144</b>, executing the media content event prediction logic <b>156</b>, accesses information in the client information database <b>158</b> to identify any predicted requesting media devices <b>102</b> that should also concurrently receive the requested media content event from the first edge server <b>104</b>.
p-0058Initially, the sub-groups of media devices <b>102</b> that are configured to establish a communication link with the first edge server <b>104</b> receiving the requested media content event are identified. In other embodiments, those media devices <b>102</b> that are able to establish a communication link <b>112</b> to the first edge server <b>104</b> are identified.
p-0059Then, for the identified media devices <b>102</b>, media content event characteristics associated with the requested media content event are compared with the learned preferred media content event characteristics of the identified media devices <b>102</b> of the sub-group. When a correlation between the media content event characteristics of the requested media content event is made with the learned preferred media content event characteristics of a particular media device <b>102</b>, that media device <b>102</b> is identified as a predicted requesting media device <b>102</b>. The identifier of that identified media device (now identified as a predicted requesting media device <b>102</b>) is communicated to the first edge server <b>104</b>.
p-0060In response to receiving the identifiers of one or more predicted requesting media devices <b>102</b>, the first edge server <b>104</b> communicates the received requested media content event to those predicted requesting media devices <b>102</b>. If a communication link <b>112</b> exists between the receiving first edge server <b>104</b> and the identified predicted requesting media device <b>102</b>, the requested media content event is sent from the first edge server <b>104</b> to the predicted requesting media device <b>102</b> over the established communication link <b>112</b>.
p-0061In the event that the communication link <b>112</b> is not currently established between the receiving first edge server <b>104</b> and the identified predicted requesting media device <b>102</b>, the receiving first edge server <b>104</b> initiates establishment of the communication link <b>112</b>. In such situations, the predicted requesting media device <b>102</b> associated with the second identifier is configured to establish a communication link over the first edge server <b>110</b> in response to receiving a request from the first edge server <b>110</b>. Any suitable process and/or protocol may be used to establish the communication link <b>112</b> between the first edge server <b>104</b> and an identified predicted requesting media device <b>102</b>.
p-0062Continuing with the above simplified illustrative example, a first requested media content event may be associated with an action media content event theme. Further, the user history prediction logic <b>154</b> has learned that the media device <b>102</b><i>a </i>is likely to request action themed media content events. The processor system <b>144</b>, executing the media content event prediction logic <b>156</b> and in response to the first requested media content event being sent to the first edge server <b>104</b>, would identify the media devices <b>102</b><i>a </i>and <b>102</b><i>b </i>as being a member of the sub-group of media devices <b>102</b> that may establish a communication link <b>112</b> with the receiving first edge server <b>104</b>. Since the media device <b>102</b><i>a </i>is likely to request action themed media content events, and since the first requested media content event has an action theme, the media device <b>102</b><i>a </i>would be identified as a predicted requesting media device <b>102</b>. In contrast, since the media device <b>102</b><i>b </i>is not likely to request action themed media content events (since action themes are not associated with the learned preferred media content event characteristics of the media device <b>102</b><i>b</i>), the media device <b>102</b><i>b </i>would not be identified as a predicted requesting media device <b>102</b>. Accordingly, the media content event access system <b>116</b> would provide the identity of the media device <b>102</b><i>a </i>to the first edge server <b>104</b> so that the first requested media content event may also be communicated to the media device <b>102</b><i>a. </i>
p-0063Continuing with the simplified illustrative example, a second requested media content event may be associated with romantic media content event theme. Further, the user history prediction logic <b>154</b> has learned that the media device <b>102</b><i>b </i>is likely to request romantic themed media content events. The processor system <b>144</b>, executing the media content event prediction logic <b>156</b> and in response to the second requested media content event being sent to the first edge server <b>104</b>, would identify the media devices <b>102</b><i>a </i>and <b>102</b><i>b </i>as being a member of the sub-group of media devices <b>102</b> that may establish a communication link <b>112</b> with the receiving first edge server <b>104</b>. Since the media device <b>102</b><i>b </i>is likely to request romantic themed media content events, and since the requested media content event has a romantic-based theme, the media device <b>102</b><i>b </i>would be identified as a predicted requesting media device <b>102</b>. In contrast, since the media device <b>102</b><i>a </i>is not likely to request action themed media content events (since romantic themes are not associated with the learned preferred media content event characteristics of the media device <b>102</b><i>a</i>), the media device <b>102</b><i>a </i>would not be identified as a predicted requesting media device <b>102</b>. Accordingly, the media content event access system <b>116</b> would provide the identity of the media device <b>102</b><i>b </i>to the first edge server <b>104</b> so that the second requested media content event may also be communicated to the media device <b>102</b><i>b. </i>
p-0064Continuing with the simplified illustrative example, a third requested media content event may have both of the actors Bob Smith and John Doe. Further, the user history prediction logic <b>154</b> has learned that the media devices <b>102</b><i>a </i>and <b>102</b><i>b </i>are likely to request media content events with these two actors. The processor system <b>144</b>, executing the media content event prediction logic <b>156</b> and in response to the second requested media content event being sent to the first edge server <b>104</b>, would identify the media devices <b>102</b><i>a </i>and <b>102</b><i>b </i>as being a member of the sub-group of media devices <b>102</b> that may establish a communication link <b>112</b> with the receiving first edge server <b>104</b>. Since the media device <b>102</b><i>a </i>is likely to request media content events with the actor Bob Smith, and since the media device <b>102</b><i>b </i>is likely to request media content events with the actor John Doe, the media devices <b>102</b><i>a </i>and <b>102</b><i>b </i>would be identified as a predicted requesting media devices <b>102</b>. Accordingly, the media content event access system <b>116</b> would provide the identity of the media devices <b>102</b><i>a </i>and <b>102</b><i>b </i>to the first edge server <b>104</b> so that the second requested media content event may also be communicated to the media devices <b>102</b><i>a </i>and <b>102</b><i>b. </i>
p-0065In some embodiments, other supplemental media content event characteristics may be associated with a particular media device. Such supplemental media content event characteristics may be stored in the client information database <b>158</b> or in another suitable memory. The supplemental media content event characteristics may be used in determining whether a requested media content event should also be sent to a particular media device when it is identified as a predicted requesting media device <b>102</b>. For example, the media device <b>102</b><i>a </i>may historically tend to have a preference for high definition format media content events. In contrast, media device <b>102</b><i>b </i>may tend to have a preference for standard definition media content events. If a high definition format requested media content event is sent to the first edge server <b>104</b>, and if the media device <b>102</b><i>a </i>is identified as a predicted requesting media device <b>102</b>, then the high definition format requested media content event may also be sent to the media device <b>102</b><i>a</i>. In contrast, since the media device <b>102</b><i>b </i>is not associated with high definition format media content events, the media device <b>102</b><i>b </i>would not be identified as a predicted requesting media device <b>102</b>.
p-0066In the various embodiments, the user history prediction logic <b>154</b> may employ any suitable algorithm, or multiple algorithms, for learning about user preferences that are associated with the media devices <b>102</b><i>a</i>-<i>i</i>. Selection of media content event characteristics for use in predicting user preferences may be based on any characteristic that may be associated with media content events. Further, any suitable number of media content event characteristics may be used to predict user preferences.
p-0067Information pertaining to user selection of media content events may be obtained from one or more sources. Alternatively, or additionally, information pertaining to media content events requested by particular media devices <b>102</b> may be obtained from the sources. In an example embodiment, information corresponding to user selection (or selection by an associated media device <b>102</b>) of premium media content events that are provided on a pay-for-view basis is provided by the media content provider. For example, the purchase of pay-per-view media content events, such as movies, sporting events, or the like, may be tracked by the media content provider, and then the associated information may be communicated to the media content event access system <b>116</b>. Alternatively, or additionally, the media content provider may provide information pertaining to the media content event characteristics of purchased media content events.
p-0068Alternatively, or additionally, information pertaining to user selection of media content events may be obtained from each one of the media devices <b>102</b><i>a</i>-<i>i</i>. For example, information may be obtained from user selection of media content events made while using a graphical user interface, such as a program guide or the like. Alternatively, or additionally, information identifying media content events stored on the DVR of the media device <b>102</b> may be provided to the media content event access system <b>116</b> by the media devices <b>102</b>. The media device <b>102</b> may provide the title or other identifier of a user selected media content event to the media content event access system <b>116</b>. The media content event access system <b>116</b> may then look up or obtains media content event characteristics associated with the identified media content event. Alternatively, or additionally, the media device <b>102</b> may provide supplemental information pertaining to a selected media content event, such as meta data, to the media content event access system <b>116</b>. The supplemental information may be used as the media content event characteristics and/or may be correlated with other media content event characteristics that are used to determine user preferences.
p-0069Alternatively, or additionally, information that may be used to determine user preferences may be obtained from a third party. For example, a history of user purchases and rentals from a media content event provider of digital video discs (DVDs) may be obtained. The user's DVD purchase and/or DVD rental history may then be processed to determine the plurality of preferred media content event characteristics associated with the user. When a user identifier (such as a name, account number, drivers license, or the like) has been associated with the identifier of a particular media device <b>102</b>, then such information may be used to determine user preferences.
p-0070Alternatively, or additionally, information that may be used to determine user preferences may be provided by the users themselves. For example, the user may provide information by answering questions on a questionnaire and/or may select preferences of interest from a list of preferences. The questionnaire and/or list of preferences of interest may be presented to the user on a graphical user interface presented on the media presentation device <b>107</b> and/or may be in hard copy form that is mailed to the media content provided or another entity for processing. A user identifier (such as a name, account number, drivers license, or the like) of the user providing the information may be associated with a particular media device <b>102</b>.
p-0071<figref idrefs="DRAWINGS">FIG. 2</figref> is a block diagram of an exemplary media device <b>102</b>. The exemplary media device <b>102</b> is communicatively coupled to a media presentation system <b>107</b> that includes a visual display device <b>202</b>, such as a television (hereafter, generically a TV), and an audio presentation device <b>204</b>, such as a surround sound receiver (hereafter, generically, a speaker). Other types of output devices may also be coupled to the media device <b>102</b>, including those providing any sort of stimuli sensible by a human being, such as temperature, vibration and the like. The video portion of the media content event is displayed on the display <b>206</b> and the audio portion of the media content event is reproduced as sounds by one or more speakers <b>208</b>. In some embodiments, the media device <b>102</b> and one or more of the components of the media presentation system <b>106</b> may be integrated into a single electronic device.
p-0072The non-limiting exemplary media device <b>102</b> comprises a media content stream interface <b>210</b>, a processor system <b>212</b>, a memory <b>214</b>, a program buffer <b>216</b>, an optional storage medium (such as, but not limited to, a digital video recorder (DVR)) <b>218</b>, a presentation device interface <b>220</b>, a remote interface <b>222</b>, and an edge server interface <b>224</b>. The processor system <b>212</b> is communicatively coupled to at least the media content stream interface <b>210</b> and the edge server interface <b>224</b>, and is controllably coupled at least to the DVR <b>218</b>. The memory <b>214</b> comprises portions for storing the media device logic <b>226</b>, the electronic program guide (EPG) information <b>228</b> optional user media content event (MCE) selection information database <b>230</b>, and the optional user history prediction logic <b>232</b>. In some embodiments, the video device logic <b>226</b> and the user history prediction logic <b>232</b> may be integrated together, and/or may be integrated with other logic. Other media devices <b>102</b> may include some, or may omit some, of the above-described media processing components. Further, additional components not described herein may be included in alternative embodiments.
p-0073The DVR <b>218</b> comprises at least two portions <b>234</b> and <b>236</b>. The user accessible portion <b>234</b> is user accessible and may be used to store user specified media content events. In an example embodiment, the other portion is hidden from the user. That is, the user is not able to independently access the hidden portion <b>236</b> and/or access a listing of the stored contents of the hidden portion <b>236</b>. Media content events received from the first edge server <b>104</b> are stored in the user inaccessible hidden portion <b>236</b> if the user is not to have independent access to the received media content events. Prior to accessing a stored media content event stored in the hidden portion <b>236</b>, the user must first obtain access authorization from the media service provider. Access authorization may be provided in any suitable manner. Once the access authorization has been granted, the requested media content event may be immediately retrieved from the hidden portion <b>234</b> for presentation to the user.
p-0074However, some media content events received from the first edge server <b>104</b> may be stored in the user accessible portion <b>234</b>, and thus be accessible by the user. Received media content events stored on the user accessible portion <b>234</b> may be freely available type media content events, such as a previously broadcasted television show, movie, news cast, sporting event or the like. Accordingly, the media device <b>102</b> may access the requested media content event from the user accessible portion <b>134</b> immediately in response to a user request for presentation of the stored media content event. Thus, a virtual video on demand for providing access to free programming may be emulated by the media devices <b>102</b>.
p-0075The functionality of the media device <b>102</b>, here a set top box, is now broadly described. A media content provider provides media content that is received in one or more multiple media content streams <b>122</b> multiplexed together in one or more transport channels. The transport channels with the media content streams <b>122</b> are communicated to the media device <b>102</b> from a media system sourced from the remote media content broadcast facility <b>106</b> (<figref idrefs="DRAWINGS">FIG. 1</figref>) operated by the media content provider. Non-limiting examples of such media systems include satellite systems, cable system, and the Internet. For example, if the media content provider provides programming via a satellite-based communication system, the media device <b>102</b> is configured to receive one or more broadcasted satellite signals detected by an antenna (not shown). Alternatively, or additionally, the media content stream <b>104</b> can be received from one or more different sources, such as, but not limited to, a cable system, a radio frequency (RF) communication system, or the Internet.
p-0076The one or more media content streams <b>122</b> are received by the media content stream interface <b>210</b>. One or more tuners <b>238</b> in the media content stream interface <b>210</b> selectively tune to one of the media content streams <b>122</b> in accordance with instructions received from the processor system <b>212</b>. The processor system <b>212</b>, executing the media device logic <b>226</b> and based upon a request for a media content event of interest specified by a user, parses out media content associated with the media content event of interest. The media content event of interest is then assembled into a stream of video and/or audio information which may be stored by the program buffer <b>216</b> such that the media content can be streamed out to components of the media presentation system <b>107</b>, such as the visual display device <b>202</b> and/or the audio presentation device <b>204</b>, via the presentation device interface <b>220</b>.
p-0077Alternatively, or additionally, the parsed out media content may be saved into the portion <b>234</b> of the DVR <b>218</b> for later presentation. The storage device, such as the example DVR <b>218</b> or another storage medium, may be directly provided in, locally connected to, or remotely connected to, the media device <b>102</b>. In alternative embodiments, the media content streams <b>122</b> may be stored for later decompression, processing and/or decryption.
p-0078From time to time, information populating the EPG information <b>228</b> portion of the memory <b>214</b> is communicated to the media device <b>102</b>, via the media content stream <b>104</b> or via another suitable media. The EPG information <b>228</b> portion stores the information pertaining to the scheduled programming. The information may include, but is not limited to, a scheduled presentation start and/or end time, a program channel, and descriptive information. The program's descriptive information may include the title of the program, names of performers or actors, date of creation, and a summary describing the nature of the program. Any suitable information may be included in the program's supplemental information. Upon receipt of a command from the user requesting presentation of an EPG <b>240</b> on the display <b>206</b>, the information in the EPG information <b>228</b> is retrieved, formatted, and then presented on the display <b>206</b> as an EPG <b>240</b>.
p-0079In the various embodiments, the EPG <b>240</b> may be modified to present a listing of available media content events that may be selected by the user. A listing of the available media content events may be stored as information in the EPG information or may be separately stored in the memory <b>214</b>. Alternatively, or additionally, the media device <b>102</b> may be operated to establish a communication link (not shown) to the media content event access system <b>116</b> or another remote device where information pertaining to the available media content events may be retrieved.
p-0080The exemplary media device <b>102</b> is configured to receive commands from a user via a remote control <b>242</b>. The remote control <b>242</b> includes one or more controllers <b>244</b>. The user, by actuating one or more of the controllers <b>244</b>, causes the remote control <b>242</b> to generate and transmit commands, via a wireless signal <b>246</b>, to the media device <b>102</b>. The commands control the media device <b>102</b> and/or control the media presentation devices <b>128</b>. The wireless signal <b>246</b> may be an infrared (IR) signal or a radio frequency (RF) signal that is detectable by the remote interface <b>116</b>.
p-0081The processes performed by the media device <b>102</b> relating to the processing of the received media content stream <b>122</b> and communication of a presentable media content event to the components of the media presentation system <b>107</b> are generally implemented by the processor system <b>212</b> while executing the media device logic <b>226</b>. Thus, the media device <b>102</b> may perform a variety of functions related to the processing and presentation of one or more media content events received in the media content stream <b>122</b> and/or stored in the DVR <b>218</b>.
p-0082Some embodiments of the media device <b>102</b> are configured to communicate with devices operated by the media content provider. For example, if a media content event is of interest to a user of the media device <b>102</b>, and the media content event is a pay-for-view type of event, the user may electronically purchase the pay-for-view media content event by operating the media device <b>102</b>. Accordingly, the media service provider is aware of those pay-for-view media content events purchased at the media device <b>102</b>.
p-0083When user media content event selection history is provided to the media content event access system <b>116</b> by the media service provider, the information may be based on the pay-for-view media content events purchased at the media device <b>102</b>. Accordingly, the media content event access system <b>116</b> may use the provided information to generate the user information that is saved into the client information database <b>158</b>.
p-0084Alternatively, or additionally, information pertaining to all types of selected media content events may be stored by the media device <b>102</b>. For example, when a user selects a media content event by navigating about the presented EPG <b>240</b>, information pertaining to the user selections may be stored in the user media content event selection information database <b>230</b> portion of the memory <b>214</b>. For example, titles of other identifiers of selected media content events may be saved into the user media content event selection information database <b>230</b>. Alternatively, or additionally, if information corresponding to the media content event characteristics of selected media content events is available, that information may optionally be saved into the user media content event selection information database <b>230</b>.
p-0085In such embodiments that save user selection information into the user media content event selection information database <b>230</b>, the information may be periodically downloaded to the media content event access system <b>116</b> or to another device. For example, the edge server interface <b>214</b>, or another interface, may be configured to periodically establish a communication link to a remote device under the control of the media content service provider of another entity to receive software updates or other information. The information pertaining to the user selections of media content events may then be downloaded from the media content event selection information database <b>230</b> portion of the memory <b>214</b> to the connected device.
p-0086Alternatively, or additionally, the media device <b>102</b> may initiate establishment of the links <b>112</b>, <b>120</b>, <b>118</b> so as to directly connect to the media content event access system <b>116</b>. Once communications are established between the media device <b>102</b> and the media content event access system <b>116</b>, the information pertaining to the user selections of media content events may then be downloaded from the media device <b>102</b> to the media content event access system <b>116</b>. Further, the information pertaining to the user selections of media content events may be downloaded from the media device <b>102</b> to the media content event access system <b>116</b> any time a media content event is received from the first edge server <b>104</b>.
p-0087Some embodiments of the media device <b>102</b> may be configured to determine user preferences. The processor system <b>212</b>, executing the user history prediction logic <b>232</b>, may access information stored in the user media content event selection information database <b>230</b>. The accessed information is analyzed to determine media content event characteristics that are of interest to the user. The determined user preference information may be saved into the user media content event selection information database <b>230</b> or into another portion of the memory <b>214</b> or into another memory. Once communications are established between the media device <b>102</b> and the media content event access system <b>116</b>, the determined user preference information may then be downloaded from the media device <b>102</b> to the media content event access system <b>116</b>. Further, the determined user preference information may be downloaded from the media device <b>102</b> to the media content event access system <b>116</b> any time a media content event is received from the first edge server <b>104</b>
p-0088In some embodiments, the media device <b>102</b> may receive a user request for a particular requested media content event, such as when the user is navigating about a presented EPG <b>240</b> which lists available media content events. Prior to accessing the requested media content event from a remote device, the media device <b>102</b> may optionally check the first edge server <b>104</b> to determine if the requested media content event is already residing on the memory of the first edge server <b>104</b>. If the requested media content event, or a portion of the requested media content event, is already at the first edge server <b>104</b>, then the requested media content event (or portion thereof) may be retrieved from the first edge server <b>104</b>. In the event that a portion of the requested media content event is available at the first edge server <b>104</b>, the amount of data to obtain the entire requested media content event will be reduced, thereby conserving communication system resources.
p-0089In some embodiments, an initial portion of a requested media content event is sent to predicted requesting media devices <b>102</b>. Accordingly, when the user of the media device <b>102</b> requests the media content event, the initial stored portion of the media content event may be presented to the user while the remaining portion of the media content event is accessed from another remote media content delivery device or from the media content event access system <b>116</b>. When presentation of the stored initial portion of the media content event has concluded, then presentation of the retrieved remaining portion begins. An unexpected benefit of this embodiment is that memory capacity of the media device <b>102</b> which is used for storing only the initial portion of the requested media content event may be reduced (as compared to storing the entirety of the media content event at the media device <b>102</b>). Accordingly, initial portion for a greater number of different available media content events can be received from the first edge server <b>104</b> and stored in the hidden portion <b>236</b> and/or the user accessible portion <b>234</b> of the DVR <b>218</b> (since storage of a very large number of media content events in their entirety at the media device <b>102</b> may not be practical or even possible).
p-0090Various embodiments of the automatic content download manager system <b>100</b> may be configured to cooperatively operate with other methods and apparatuses which operate the media devices <b>102</b>. For example, the automatic content download manager system <b>100</b> may cooperatively operate with a video on demand system. As another example, the automatic content download manager system <b>100</b> may operate in cooperation with a maintenance system which updates and/or downloads software to the media devices <b>102</b>.
p-0091It should be emphasized that the above-described embodiments of the automatic content download manager system <b>100</b> are merely possible examples of implementations of the invention. Many variations and modifications may be made to the above-described embodiments. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.
Contents4
3 sheets
Sheet 1 Sheet 2 Sheet 3
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2020228452A1 | Cited by | United States of America | Search report |
| US12052444B2 | Cited by | United States of America | Applicant |
| US11503345B2 | Cited by | United States of America | Applicant |
| US10924417B2 | Cited by | United States of America | Search report |
| US9888274B2 | Cited by | United States of America | Applicant |
| US11381619B2 | Cited by | United States of America | Applicant |
| US2005005303A1 | Cites | United States of America | Search report |
| US2007198689A1 | Cites | United States of America | Search report |
| US2008276266A1 | Cites | United States of America | Search report |
| US2009298525A1 | Cites | United States of America | Search report |
| US2010017822A1 | Cites | United States of America | Search report |
| US2010325675A1 | Cites | United States of America | Search report |
| US2011127202A1 | Cites | United States of America | Search report |
| US2012018528A1 | Cites | United States of America | Search report |
| US2012110074A1 | Cites | United States of America | Search report |
| US7454485B2 | Cites | United States of America | Search report |
| US7664854B2 | Cites | United States of America | Search report |
| US7761542B2 | Cites | United States of America | Search report |
| US8081957B2 | Cites | United States of America | Search report |
| US8108939B2 | Cites | United States of America | Search report |
| US8363666B2 | Cites | United States of America | Search report |
8 members in 1 office; this record represents the family
Members8
| Document | Office | Kind | |
|---|---|---|---|
| US2013185382A1 | United States of America | A1 | |
| US8930491B2This record | United States of America | B2 | |
| US2015127780A1 | United States of America | A1 | |
| US10063605B2 | United States of America | B2 | |
| US2019014164A1 | United States of America | A1 | |
| US10764344B2 | United States of America | B2 | |
| US2020351319A1 | United States of America | A1 | |
| US11381619B2 | United States of America | B2 |
65 transactions on the USPTO file
Allowed after 1 non-final rejection, 1 final rejection and 1 RCE.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 12th Year, Large EntityM1553 | M1553 | |
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Post Issue Communication - Certificate of CorrectionN423 | N423 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Correspondence Address ChangeC.AD | C.AD | |
| Response to Reasons for AllowanceREAS | REAS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Interview Summary- Applicant InitiatedEXIA | EXIA | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| New or Additional Drawing FiledC614 | C614 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| PILOT- Request for After Final Consideration ProgramRAFC | RAFC | |
| New or Additional Drawing FiledC614 | C614 | |
| Response after Final ActionA.NE | A.NE | |
| Mail Post CardPST_CRD | PST_CRD | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Email NotificationEML_NTR | EML_NTR | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Email NotificationEML_NTR | EML_NTR | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Sent to Classification ContractorPGPC | PGPC | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| Applicant has submitted a new specification to correct Corrected Papers problemsCORRSPEC | CORRSPEC | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTF | EML_NTF | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Corrected PaperCPAP | CPAP | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
8 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| Certificate of correctionCC | CC | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 08930491
- Application
- 13352822
Titles
- English
- Apparatus, systems and methods for providing edge cached media content to media devices based on user history
Patent term adjustment
- A delay
- +113 daysthe office missed an examination deadline
- Applicant delay
- −61 days
- Net adjustment
- 52 days
Classification
- CPC, 10
- H04N21/251
- H04L65/60
- H04N21/254
- H04N21/25891
- H04N21/262
- H04N21/4331
- H04N21/4622
- H04L65/611
- H04L65/612
- H04L67/10
- IPC, 2
- G06F15 16
- H04N7 173
- USPC, 2
- 709217000
- 725100000