Grouping and presenting content

Information

  • Patent Grant
  • 11146849
  • Patent Number
    11,146,849
  • Date Filed
    Wednesday, January 23, 2019
    5 years ago
  • Date Issued
    Tuesday, October 12, 2021
    3 years ago
Abstract
A provider transmits instructions to a receiver to record multiple instances of content. The instances of content are included in the same frequency band of a broadcast signal transmitted via a first communication link and encoded utilizing a common encryption. The provider determines to supplement and transmits an instruction to record a supplemental instance of content from a second content provider via a second communication link. The receiver receives the instructions and accordingly receives, decodes, and stores the multiple instances of content and the supplemental content. A recorder in communication with the receiver determines whether a content selection is a member of a content group. The group determination is based on a tag of the content selection. If the content selection is a member of the content group, the recorder presents to a display device the content selection and at least one other member of the content group.
Description
FIELD OF THE INVENTION

This disclosure relates generally to content receivers, and more specifically to presenting content from a content receiver.


BACKGROUND

Audio/visual recorders for broadcast content, e.g., television shows, may include a digital video disc burner or digital video recorder. These recorders may be programmed to record various broadcast content and store the content as the content is broadcast. These recorders may not provide a way to link content together or present content in an order other than the order it was recorded.


SUMMARY

The present disclosure discloses systems and methods content presentation. In one example, a content provider transmits instructions to a content receiver to record multiple instances of content. The instances of content are included in the same frequency band of a broadcast signal transmitted by the content provider via a first communication link and encoded utilizing a common encryption. The content provider determines to supplement the multiple instances of content and transmits an instruction to record a supplemental instance of content from a second content provider via a second communication link. The content receiver receives the instructions and accordingly receives, decodes, and stores the multiple instances of content and the supplemental instance of content. A digital video recorder in communication with the content receiver determines whether a content selection by a user is a member of a content group. The group determination is based on a tag of the content selection. If the content selection is a member of the content group, the digital video recorder presents to a display device the content selection and at least one other member of the content group.


In various implementations, a method of presenting content stored on a content receiver is disclosed. The method may include receiving, at a content receiver a plurality of instructions to simultaneously record a plurality of instances of content each of the plurality of instances corresponding to a separate content provider. After the content has been received, the method may include recording, utilizing the content receiver, at least one of the plurality of instances of content via the least one first communication link as specified by the plurality of instructions. Then, receiving a content selection at an input to the content receiver and determining at the content receiver whether the content selection is a member of a group. If the content selected is a member of the group, the method may include presenting at least a first content member and a second content member of the group in a predetermined order corresponding to an episode identifier.


It is to be understood that both the foregoing general description and the following detailed description are for purposes of example and explanation and do not necessarily limit the present disclosure. The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate subject matter of the disclosure. Together, the descriptions and the drawings serve to explain the principles of the disclosure.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram illustrating a system for automatically recording multiple instances of content from one or more programming providers.



FIG. 2 is a block diagram illustrating a system for providing electronic programming guides that combine stored content information with content provider schedule information.



FIG. 3 is a diagram illustrating a first example of an electronic programming guide that may be provided by the system of FIG. 1.



FIG. 4 is a flow chart illustrating a method of grouping and recording content.



FIG. 5 is a flow chart illustrating a method of presenting related content.





DETAILED DESCRIPTION OF THE EMBODIMENTS

The description that follows includes sample systems, methods, and computer program products that embody various elements of the present disclosure. However, it should be understood that the described disclosure may be practiced in a variety of forms in addition to those described herein.


Content receivers (such as set top boxes, television receivers, digital video recorders, and so on) generally receive content from one or more programming providers (such as satellite television programming providers, cable television programming providers, Internet service providers, video on demand providers, pay-per-view movie providers, and so on) via one of more communication connections (such as satellite communication connections, coaxial cable communication connections, Internet communication connections, radio-frequency connections, and so on). Such content receivers may transmit such received content to one or more presentation devices and/or store the received content for later presentation.


When a user is viewing content previously stored on the content receiver, the user may wish to view the content according to a specific group. For example, the user may wish to view content recordings in the order that the content was originally presented. This may include a variety of different content selections that may have been originally presented on a single channel during a particular time frame. In one example, a user may wish to view all of the content originally broadcast during a primetime channel slot, on a particular channel. Current digital video recorders (DVRs) may store content by its name. Therefore, if a user wished to watch all of the content presented on a particular channel from the time of 7 pm to 10 pm, he or she would have to select each specific content (by varying names) in order to cause the DVR to present the content. Similarly, DVRs may store content based on the name and the originally broadcast date. For example, a user may wish to record content that may be a rerun of previously aired content that may be displayed on multiple channels in a random or non-chronological order. The DVR may be configured to record each content. However, the user may wish to view the content by original episode number (rather than recorded or broadcast date).


The present disclosure discloses systems and methods for grouping, recording, and/or presenting content. The content (e.g., television shows) may be grouped together based on the originally broadcast time, date, and/or channel, or based on a episode number, title, descriptor, or the like. As the content may be grouped, a user may select multiple different content to be displayed continuously. For example, the user may wish to view the content chronologically as it was originally aired on a particular channel and the content receiver may display the content in the particular order it was originally aired. In this example, content may be arranged to be displayed after one another, based on the original airing sequence, e.g., content that aired at 7 pm may be presented prior to content that aired at 7:30 pm, and so on.


In another example, the grouping or relationship may be related to an episode and/or title of a particular content. When a user selects a particular content to watch, the content may be presented based on an episode number, which may be out of order from how the content was originally recorded. For example, syndicated content may broadcast different episodes of a particular content series out of episode order. Therefore, by presenting the content based on an episode (or title) order, a user may watch all of the episodes for a particular show episodically, although the show may not have been recorded in that manner.


Users of content receivers may desire to access different instances of content that may be broadcast simultaneously and/or substantially contemporaneously by content providers. For example, many television programming viewers wish to watch different television programs that occupy the same broadcast time slot, such as the different television programs associated with the major television programs that are broadcast between 7 PM and 10 PM mountain standard time. Content receivers may attempt to address this issue by utilizing multiple tuners that can each separately present and/or record different, simultaneously broadcast instances of content. However, a separate tuner may still be required for each simultaneous or substantially contemporaneous instance of broadcast or otherwise received content that a content receiver user wishes to view and/or record. Further, in addition to separate tuners required for each instance of content, the content receiver may require sufficient resources to descramble and store each of the instances of content desired by the user.



FIG. 1 is a block diagram illustrating a system 100 for automatically recording multiple instances of content from one or more programming providers. The automatic recording of multiple instances of content provided by the system 100 may enable users of content receivers to access different instances of content that are broadcast simultaneously and/or substantially contemporaneously by content providers.


In various broadcast systems, content providers may broadcast content to a plurality of different content receivers via one or more frequency bands utilizing one or more satellites. Each multiplexed signal contained in the frequency band (sometimes referred to as a transponder) may be configured to include data related to one or more instances of content, such as one or more television programming channels. The data related to each of the programs may include multiple PIDs (packet identifiers), such as a video PID and one or more audio PIDs for a particular instance of content. The data related to each of the instances of content included in each frequency may be scrambled utilizing one or more CWs (control words), which may then be encrypted to generate one or more ECMs (entitlement control messages) which may in turn be included with the data. A content receiver may typically tune to one or more of the frequency bands to receive the multiplexed signal that contains data for a particular programming channel utilizing one or more tuners. The content receiver may process only a subset of the programming channels by keeping the data associated with the particular programming channel and discarding data received via the tuned frequency band and multiplexed signal associated with other programming channels, such as by utilizing a PID filter to keep data identified by PIDs related to the particular programming channel and discard data identified by PIDs not related to that particular programming channel. The content receiver may decrypt the ECM included with the data associated with the particular programming channel to obtain the CW, descramble the data utilizing the CW, and store and/or transmit the data (e.g., decompressed, reconstructed audio and video data) to one or more presentation devices.


As illustrated in FIG. 1, in this implementation, one or more content providers may select multiple instances of content 101 to be automatically recorded such as by utilizing predefined recording parameters. For example, a content provider may select all of the television events defined as “primetime events” associated with all channels defined as “primetime television channels” for a particular period of time defined as “prime time” to be automatically recorded. In other examples, the content provider may select television events associated with programming channels for a particular time period (such as a half hour, multiple hours, and/or an entire programming day) in response to user selections. After the content provider selects the multiple instances of content, the multiple instances of content may be multiplexed utilizing a multiplexer 102. The multiplexed signal (which includes the multiplexed selected multiple instances of content) may then be scrambled by a scrambler 105 utilizing one or more CWs 103. The CW may be encrypted to generate an ECM by an ECM generator 112 which may take the CW as an input (and may also include other information such as access criteria) and outputs the ECM, which may be included with the multiplexed signal. The scrambled multiplexed signal may then be included in a broadcast on a frequency band (e.g., cable, satellite), which may then be transmitted to one or more satellites 106 for broadcast. The satellite 106 may receive the frequency band (uplink frequency band) and then broadcast the multiplexed signal to a number of content receivers on a translated frequency band (downlink frequency band), such as a content receiver that includes a tuner 107.


The tuner 107 may tune to the frequency band that includes the multiple instances of content (which may be performed in response to one or more recording instructions received by the content receiver that includes the tuner from the content provider). The data received via the tuned frequency (which may be filtered by a PID filter, not shown) may be demultiplexed by a demultiplexer 109 and then descrambled by a descrambler 110 utilizing the CW before being stored in a non-transitory storage medium 111 (which may take the form of, but is not limited to, a magnetic storage medium; optical storage medium; magneto-optical storage medium; read only memory; random access memory; erasable programmable memory; flash memory; and so on) based on recording parameters, such as predefined recording parameters. The demultiplexer 109 may obtain the included ECM 104, and the ECM may be provided to a smart card 108 that may decrypt the ECM 104 to obtain the CW 103 for the descrambler 110. Hence, the multiple instances of content may subsequently all be available to a user of the content receiver (until such time as they are removed from the non-transitory storage medium) without requiring multiple tuners to receive each of the multiple instances of content, without requiring the smart card to decrypt multiple ECMs. In some implementations, the multiple instances of content may be stored in a single file.


Although the system 100 is illustrated in FIG. 1 and is described above as including a number of specific components configured in a specific arrangement, it is understood that this is for the purposes of example and other arrangements involving fewer and/or additional components are possible without departing from the scope of the present disclosure. For example, in various implementations, the multiple instances of content may be individually scrambled utilizing the CW prior to multiplexing. In another example, in some implementations, the data received via the tuned frequency may be demultiplexed before being individually descrambled utilizing the CW.


In some implementations of the system of FIG. 1, multiple instances of content may be recorded simultaneously from a single transponder and stored in the non-transitory storage medium 111 of the content receiver as a single file of multiple recorded instances of content. Upon playing of one instance of content from the single file of the multiple recorded instances of content, the content receiver may read the file incrementally so as to play the one instance of content while filtering out the other file contents (e.g., the other instance of content within the file).



FIG. 2 is a block diagram illustrating a system 200 for grouping, recording, and/or presenting content. The system 200 includes a content receiver 201 which may be a set top box, a television receiver, a digital video recorder, a digital music player, a desktop computer, a laptop computer, a tablet computer, a mobile computer, a cellular telephone, a smart phone, and/or any other electronic device that is able to receive and/or provide received content. The system 200 may also include one or more content providers 202 (such as one or more satellite television programming providers, cable television programming providers, Internet service providers, video on demand providers, pay-per-view movie providers, and/or other entities that are configured to transmit instances of content to the content receiver) and/or one or more presentation devices 203 (such as one or more cathode ray tube displays, computer monitors, liquid crystal displays, televisions, speakers, and/or other devices configured to present instances of content transmitted by the content receiver).


The content receiver 201 may include one or more processing units 204 (which may perform functions and/or include components (not shown) that perform functions corresponding to the smart card 108, the descrambler 109, and/or the demultiplexer 109 of FIG. 1), one or more non-transitory storage media 205, one or more communication components 206 (which may include, but is not limited to, the tuner 107 of FIG. 1), one or more output components 207, and one or more user interface components 208.


The processing unit 204 may execute instructions stored in the non-transitory storage medium 205 to receive one or more instances of content, instructions to record such instances of content, and/or EPG data from the content provider 202 via one or more communication links (such as one or more satellite communication connections, coaxial cable communication connections, Internet communication connections, radio-frequency connections, and/or other communication links) utilizing the communication component and/or store such content in the non-transitory storage medium (which may be at the direction of one or more instructions received from the content provider that specify to record received instances of content).


The processing unit 204 may also execute instructions stored in the non-transitory storage medium 205 to transmit instances of content received from the content provider 202 and/or stored in the non-transitory storage medium to the presentation device 203 utilizing the output component. In one or more cases, the processing unit may execute the instructions described above in response to one or more user instructions received from one or more user input/output devices (not shown) (such as one or more remote control devices, touch screens, buttons, keyboards, mice, and/or other input/output devices) via the user interface component 208.


Additionally, the processing unit 204 may execute instructions stored in the non-transitory storage medium 205 to transmit one or more EPGs to the presentation device 203 via the output component 207 (which may be performed in response to one or more user instructions received via the user interface component 208). The EPG may include schedule information for one or more instances of content accessible by the content receiver 201 from the content provider 202. The schedule information for the instances of content may be configured in the EPG as slots in a grid arranged by time associated with the respective instance of content and source (such as channel) associated with the respective instance of content. In some cases, the EPG may include one or more additional information fields that may present additional information regarding an instance of content (such as a program description and other program information for a television program) when user selection of a slot corresponding to the instance of content is received via the user interface component 208.


The processing unit 204 may determine whether or not one or more instances of recorded content are stored in the non-transitory storage medium 205. If so, the processing may incorporate content information for one or more of the instances of recorded content in the EPG. The content information that the processing unit incorporates in the EPG may include, but is not limited to, one or more portions of the instance of recorded content such as one or more images and/or one or more video segments and/or one or more images and/or video segments related to the instance of recorded content. The processing unit may obtain the portion of the instance of content and/or the image or video segment related to the instance of recorded content (such where the instance of content is an episode of a television series and the processing unit obtains an image from a future episode) to include in the content information by processing the instance of content stored in the non-transitory storage medium and/or by receiving images and/or video segments from the content provider.


In some implementations, the processing unit 204 may be configured to always include content information for one or more instances of recorded content when such instances of recorded content are stored in the non-transitory storage medium 205. For example, the processing unit may include a field in the EPG that includes content information for each of the instances of recorded content stored in the non-transitory storage medium. In other implementations, the processing unit may provide an EPG that does not include such content information and may incorporate the content information after receiving a user selection of one of more slots of the EPG via the user interface component 208. The content information incorporated in response to the user selection of the slot may correspond to one or more recorded instances of content stored in the non-transitory storage medium that are associated with the instance of content that corresponds to the slot.


Regardless of whether the processing unit 204 incorporates the content information prior to user input or in response to user input, the processing unit may be configured to perform one or more actions in response to receiving a user selection of the content information incorporated into the EPG. For example, in some implementations the processing unit may incorporate additional information related to the instance of recorded content corresponding to the selected content information into the EPG. Such additional information may include, but is not limited to, descriptions of the instance of content, ratings of the instance of content, information about the number of related instances of content are stored on the non-transitory storage medium 205 (such as where the instance of content is an episode of a particular television series and the additional information includes the number of episodes of that particular television series that are stored in the non-transitory storage medium), and/or other such information related to the particular instance of content. By way of another example, in some implementations the processing unit may be configured to access an instance of content that corresponds to the selected content information from the non-transitory storage medium.


In various implementations, the instances of recorded content for which the processing unit 204 incorporates content information in the EPG may be the multiple instances of content 101 selected to be automatically recorded as illustrated in FIG. 1 and described above. The content receiver 201 may have automatically recorded the multiple instances of content 101 in response to receiving instructions to record the multiple instances of content 101 from the content provider 202. When providing the EPG, the processing unit may include content information for each of the multiple instances of content 101. In various other implementations, the instances of recorded content for which the processing unit 204 incorporates content information in the EPG may be instances of content which the processing unit has recorded in response to user input received via the user interface component 208 such as recorded broadcast content, recorded video on demand content, recorded pay-per-view content, and so on.



FIG. 3 is a diagram of an example EPG programming that may be generated by the processing unit 204 of the content receiver 201. The EPG 300 may be display data 302 related to content, which in this example is audio visual programming content. The data 302 may vary depending on the content. For example, the EPG 300 may include information relating to content that may be presented at a variety of different time slots, e.g., from 7 pm to 10 pm. The data 302 for each time slot may vary, as the content varies. The data 302 may include a title 306, an episode identifier 308, a description 310, and so on. It should be noted that the data 302 may be displayed on the EPG 300 and/or may be included or attached to the content (e.g., as metadata associated with the content). As such, the depiction of the EPG 300 is merely exemplary and is not meant to be limiting (and in some instances may not be needed).


The data 302 may vary for each selected content. For example, different content instances may include the same title 306, but the episode identifier 308 may be varied. Continuing the example, data 302 for the first content listed in the EPG 300 may have the same title 306 as the content 318 listed for the 10 pm time slot, but the episode numbers 308, 320 may be different. Both instances of the content may be instances of a television show or series, and thus may have the same title, but may be different episodes of the same show, e.g., episode 1 and episode 4. The episode identifier 308, 320 may be used to indicate the order of the particular content with respect to an entire season and/or series of the content.


The episode identifier 308, 320 allows instances where the content may be re-run, syndicated, or otherwise presented at different times and dates to be related to the original presentation order. The episode identifier 308, 320 may allow a user watching instances of a particular content series to determine if he or she is viewing the instance in the original presentation order or in another order. Similarly, the description 310 may provide a user with substantially any desired information with respect to the content, e.g., actors that may be in the content, a description of the content episode, and so on.


It should be noted that the data 302 for each content may further include the time slot 304 and/or date in which the content is (or was) presented. This may allow the content receiver 201 (or other unit) to determine when the content was originally presented, which may allow the content receiver 201 to replay the content in the original presentation order (e.g., chronological and/or series). This is discussed in more detail below with respect to FIG. 5. Furthermore, it should be noted that the data 302 may include multiple other types of information and/or may vary based on the type of content. Therefore, the different data 302 categories listed are meant to be exemplary and not limiting.



FIG. 4 is a flow diagram illustrating a method 400 for grouping content. The method 400 may begin with operation 402 in which content is selected to be recorded. Operation 402 may be completed by a user providing input to the content receiver 201 indicating that he or she wishes to record or store an additional content, or the content may be selected by the content receiver 201. For example, as shown in FIGS. 1 and 2, the content receiver 201 may record content corresponding to a selected time slot or series of time slots, e.g., “primetime.” Once particular content is selected to be recorded, the method 400 may proceed to operation 414. In operation 414 the content receiver 201 records the content. In some instances, the content may be automatically recorded, without requiring an input by the user.


Once the content is recorded, the method 400 proceeds to operation 404. Operation 404 determines whether the selected content is part of a group. The group may be defined by substantially any type of criteria, e.g., title 306, episode identifier 308, time slot 304, description 310, channel and so on. Furthermore, the group may correspond to a user input, e.g., content related to historical shows, sports, home and garden, and so on. If the content is not part of a group, but rather a discrete content selection, the method 400 may proceed to operation 404 and the selected content may be recorded, e.g., by the content receiver 201. If, however, the content is part of a group, the method 400 may proceed to operation 406.


Operation 406 may tag the content with data relating to the group. It should be noted that in some instances the content may be already tagged with the selected data, e.g., data 302 may provide sufficient information (title 306, episode identifier 308, description 310, time slot 304) to group the content or relate the content to other content. However, in other instances, the grouping may be selected by the user or the content receiver 201 (e.g., all content for a group of time slots 304). Therefore, the content receiver 201 may tag (or additionally tag) the content with the data relating to its particular group.


The content receiver 201 may tag the content with data relating to the group by inserting metadata into the electronic file storing the content, by changing another characteristic of an electronic file of the content, or the like. Additionally or alternatively, the content may be tagged with data relating the group and may also be indexed by the content receiver 201. Once the content is tagged, the method 400 may proceed to operation 408.


Operation 410 may search for related content, e.g., by scanning the data 302 provided for each content, and may then return to operation 402. The relatedness of content may be determined by similar data 302, such as the same title 306, broadcast channel, descriptor 310, or the like. Operation 410 may be performed by scanning or searching already recorded content on the content receiver 201, currently broadcasted content, and/or content presented on the EPG that may be broadcast in the future.


Operation 408 determines whether the other group members should be recorded. In one example, the content receiver 201 may be configured to present an option to the user on whether he or she wishes to record the related content. In another example, the content receiver 201 may make a determination (based on the type of group, whether the other content has been previously recorded, and so on), whether the other content should be recorded. If, in operation 408 the other group members are to be recorded, the method 400 may proceed to operation 410. If the content is to be recorded, the method 400 may return to operation 402, so that the method 400 may repeat until all related, available and/or desired content may be recorded.


As briefly described above, the method 400 illustrated in FIG. 4 is merely one option of tagging content and/or grouping content together. In some instances, the content may be grouped together based on the data 302 provided and/or displayed in the EPG 300. Similarly, the method 400 of FIG. 4 may be used to enhance or add to the data 302 provided in the EPG 300, e.g., based on user's preferences, and the like.



FIG. 5 is a flow chart illustrating a method for displaying, recording and/or presenting content. The method 500 may be configured to selectively present content depending on whether the content is part of a group, or otherwise related to other content. The method 500 may begin with operation 502 which determines whether a group of content should be presented. For example, the content receiver 201 may present an option to a user to watch a select content/group of content, a user may select a content to watch, or the like. If the group of content is not selected to be viewed, the method 500 may proceed to operation 509 and the single instance of content may be presented. For example, the user may select a particular content and then the method 500 may present whether the user may wish to view the entire group of content. However, in some instances the user may wish to only view a particular content instance and therefore in operation 509, only the single content instance may be played.


If in operation 502 the group of content is selected to be watched, the method 500 may proceed to operation 504 and the content may be retrieved. For example, the content may be stored by the content receiver 201 as part of a block storage of particular time slots 304 and/or may be stored separately as a discrete recording or other type of storage within the content receiver 201 (e.g., a series specifically selected by the user to be recorded).


Once the content is retrieved, the method 500 may proceed to operation 506, and the content may be presented. The content receiver 201 may communicate the content to a display device, such as a television, or the content receiver 201 itself may present the content, and so on. After or as the content is being presented, the method 500 may proceed to operation 507 and the content may be tagged as being viewed. For example, the content receiver 201 may place a metadata tag on the content indicating that the content has been viewed at least once.


After the content has been presented and tagged as being viewed, the method 500 may proceed to operation 508. Operation 508 determines whether the content is part of a group. As described above with respect to FIG. 4, the content may be selectively tagged with data that may indicate membership in a group or another relationship between selected content. The group may be determined by the time slot 304 that the content was originally presented. For example, content displayed in the time slots 304 corresponding to 7 pm to 10 pm may be grouped together as the primetime slots for a particular day. In another example, the content may be selectively grouped together based on the title of the content, e.g., each episode of a particular television show may be grouped together as belonging to a group corresponding to the television show. In still another example, the content may be grouped together based on the episode identifier 308. If the content is not part of a group, the method 500 may end, but if the content is part of a group the method 500 may proceed to operation 510.


Operation 510 determines whether there is other content within the group. Operation 510 may determine whether there is other content recorded on the content receiver 201. For example, the content receiver 201 may utilize a lookup table or other index to determine content relationships, and if a particular content instance is a member of a group. In another example, the content may include a forward pointer and/or a backward pointer to indicate a relationship with other content, e.g., a forward pointer indicating the prior content and a backward pointer indicating a following content. In some instances, every content recording may be stored in a different file for a particular section of time slots. For example, every content instance from 7 pm to 10 pm for a particular day may be stored in a single electronic file on the content receiver 201. In these instances, the file may include metadata or other indicators separating each separate content instance. In other instances, the content may be stored in separate electronic files. In either instance, the content receiver 201 may determine (e.g., by searching, indexing, or the like), if there is other content in the group.


If there is other content in the group, in one embodiment, the method may proceed to optional operation 512. Optional operation 512 determines whether the other content has been viewed. For example, a user may have already viewed a selected time slot 304 and/or episode of a selected content. In this example, the method 500 may proceed to operation 512 and the previously viewed content or portions thereof may be skipped or otherwise passed over. Therefore, operation 514 may help to prevent a user from viewing content that he or she has already seen, although the content may belong to a particular group.


In some embodiments, operation 514 may be presented as an option to the user. For example, there may be some instances where a user may wish to re-watch a particular content, and/or another user may have viewed the content and the particular user may want to view it, and so on. After operation 514, the method 500 may return to operation 510, which may determine whether there is other content in the group.


If in operation 512, the method 500 determines that the other content in the group has not been viewed, the method may proceed to operation 515. Operation 515 may determine whether a stop command has been received, e.g., whether an input has been provided to the content receiver 201 indicating that a user may no longer wish to view content. If a stop command has been received, the method 500 may terminate. However, if in operation 515 a stop command has not been received, the method 500 may proceed to operation 516.


Operation 516 retrieves the additional content related to the originally selected content. For example, the content receiver 201 may retrieve (from storage) the other episodes that may correspond to a particular title 306, description 310 and the like. Additionally or alternatively, the content receiver 201 may retrieve the other content that may have originally been presented in a chronological order, e.g., by ascending time slots 304.


After operation 516, the method 500 may proceed to operation 518 and the additional content may be presented. The content receiver 201 may present the additional content selectively, e.g., a single episode at a time. The method 500 may allow for multiple shows to be grouped and presented in a variety of different manners. For example, content may be grouped by date and time but may also (or alternatively) be grouped by title 306 and/or episode identifier 308. This may allow the content receiver 201 to represent the content in a chronological order, e.g., recall and present the content as it was originally displayed on the select date in the select time slots. Additionally, the content receiver 201 may present the content based on episodes. For example, the first episode of a particular content (which may have been recorded at a later date) may be present first and a the second episode then be presented second (although it may have been recorded first).


In one embodiment, the content receiver 201 may present content originally displayed at the 7 pm time slot, then present content displayed at the 8 pm time slot and so on. In another embodiment, the content receiver 201 may present content corresponding to a particular episodic identifier 308. This embodiment may allow for content to be presented in episodically, rather than chronologically when it was presented and/or recorded. For example, episodes of a particular show may be presented out of their original order (e.g., due to syndication, re-runs, and so on). To address this, the content receiver 201 may be configured to record all of the episodes and then present the content in the original episode order.


Furthermore, as described in operation 512, the method 500 may further skip or otherwise not present content that may have already been viewed. For example, a user may have viewed content presented on a particular channel at an 8 pm time slot, but actually may be viewing stored content corresponding to the 7:30 pm slot. The content receiver 201 sequentially presents content corresponding to the 9 pm time slot, rather than the 8 pm time slot. Therefore, a user may not have to fast-forward or otherwise manually skip the content that he or she has already viewed. Similarly, a user may have viewed a particular episode of a show, but may be viewing a prior episode, the content receiver 201 may then skip the viewed episode and present the next episode, which may be based on episode identifier 308 and/or previously presented date, time slot 304 and the like.


The described disclosure may be provided as a computer program product, or software, that may include a non-transitory machine-readable medium having stored thereon instructions, which may be used to program a computer system (or other electronic devices) to perform a process according to the present disclosure. A non-transitory machine-readable medium includes any mechanism for storing information in a form (e.g., software, processing application) readable by a machine (e.g., a computer). The non-transitory machine-readable medium may take the form of, but is not limited to, a magnetic storage medium (e.g., floppy diskette, video cassette, and so on); optical storage medium (e.g., CD-ROM); magneto-optical storage medium; read only memory (ROM); random access memory (RAM); erasable programmable memory (e.g., EPROM and EEPROM); flash memory; and so on.


It is believed that the present disclosure and many of its attendant advantages will be understood by the foregoing description, and it will be apparent that various changes may be made in the form, construction and arrangement of the components without departing from the disclosed subject matter or without sacrificing all of its material advantages. The form described is merely explanatory, and it is the intention of the following claims to encompass and include such changes.


While the present disclosure has been described with reference to various embodiments, it will be understood that these embodiments are illustrative and that the scope of the disclosure is not limited to them. Many variations, modifications, additions, and improvements are possible. More generally, embodiments in accordance with the present disclosure have been described in the context or particular embodiments. Functionality may be separated or combined in blocks differently in various embodiments of the disclosure or described with different terminology. These and other variations, modifications, additions, and improvements may fall within the scope of the disclosure as defined in the claims that follow.

Claims
  • 1. A method of presenting content stored on a content receiver, the method comprising: receiving, by a tuner of a content receiver from a content provider, a multiplexed broadcast signal in a frequency band, the multiplexed broadcast signal including data related to a plurality of instances of programming content, each of the instances of programming content corresponding to a respective separate television event;recording, automatically by the content receiver, at least one of the plurality of instances of programming content to a non-transitory storage medium of the content receiver, thereby adding the set of instances of programming content to a plurality of stored instances of programming content stored on the storage medium;receiving, by the content receiver subsequent to the recording, a content selection from a user of the content receiver, the content selection including an instruction to view a requested instance of programming content;determining, automatically by the content receiver in response to the content selection, a group of instances of programming content including multiple of the plurality of stored instances of programming content identified, such that each member of the group meets a group criteria shared by each other member of the content group and by the requested instance of programming content, and the members of the group are not episodes of same episodic programming, but have an original airing sequence;determining a playback sequence in accordance with the original airing sequence indicated by the group criteria; andpresenting to the user, automatically by the content receiver in response to the content selection, an option to view the requested instance of programming content as part of the group in the playback sequence determined to be indicated by the group criteria.
  • 2. The method of claim 1, further comprising: transmitting the group of instances of programming content by the content receiver to a display device for display on the display device.
  • 3. The method of claim 2, wherein: the transmitting comprises transmitting instructions directing the content receiver to playback the members of the group of instances of programming content for display on the display device in accordance with the playback sequence.
  • 4. The method of claim 2, wherein: determining the group of instances of programming content comprises determining, for each stored instance of programming content of the plurality of stored instances of programming content, whether the stored instance of programming content has been previously viewed by a user of the content receiver; andthe transmitting comprises transmitting instructions directing the content receiver to skip playback of those members of the group determined to have been previously viewed by the user of the content receiver.
  • 5. The method of claim 1, further comprising: receiving a set of instructions by the content receiver from the content provider; anddetermining, automatically by the content receiver, the predefined recording parameters from the set of instructions.
  • 6. The method of claim 1, further comprising: receiving a selection of criteria by the content receiver from a user of the content receiver; anddetermining, automatically by the content receiver, the respective criteria from the selection of criteria.
  • 7. The method of claim 1, wherein the data related to the plurality of instances of programming content is all scrambled by a same control word.
  • 8. The method of claim 1, wherein each member of the group meets the group criteria by being associated with a same time slot during which the member of the group was originally presented.
  • 9. The method of claim 1, wherein determining the group of instances of programming content comprises: determining, for each stored instance of programming content of the plurality of stored instances of programming content, whether the stored instance of programming content has been previously viewed by a user of the content receiver; andincluding the stored instance of programming content as a member of the group in accordance with determining that the stored instance of programming content has not been previously viewed by the user of the content receiver.
  • 10. The method of claim 1, wherein each of the instances of programming content corresponds to a separate television event on a separate television channel from a separate content provider.
  • 11. The method of claim 1, wherein the receiving and recording of the group of instances of programming content by the television receiver is not in the original airing sequence.
  • 12. The method of claim 1, wherein the at least one of the plurality of instances automatically identified for recording by the content receiver based on comparing predefined recording parameters with criteria received in association with receiving the at least one of the plurality of instances.
  • 13. A television receiver, comprising: one or more processors;a plurality of tuners; anda non-transitory computer readable storage medium communicatively coupled to the one or more processors, wherein the non-transitory computer readable storage medium includes instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: receiving, by a tuner of the plurality of tuners, from a content provider, a multiplexed broadcast signal in a frequency band, the multiplexed broadcast signal including data related to a plurality of instances of programming content, each of the instances of programming content corresponding to a respective separate television event;recording at least one of the plurality of instances of programming content to a non-transitory storage medium of the content receiver, thereby adding the set of instances of programming content to a plurality of stored instances of programming content stored on the storage medium;receiving a content selection from a user of the content receiver, the content selection including an instruction to view a requested instance of programming content;determining, in response to the content selection, a group of instances of programming content including multiple of the plurality of stored instances of programming content identified, such that each member of the group meets a group criteria shared by each other member of the content group and by the requested instance of programming content, and the members of the group are not episodes of same episodic programming, but have an original airing sequence;determining a playback sequence in accordance with an original airing sequence indicated by the group criteria; andpresenting to the user, automatically by the content receiver in response to the content selection, an option to view the requested instance of programming content as part of the group in the playback sequence determined to be indicated by the group criteria.
  • 14. The television receiver of claim 13, wherein the operations further comprise: transmitting the group of instances of programming content to a display device for display on the display device.
  • 15. The television receiver of claim 14, wherein: the transmitting comprises transmitting instructions directing playback of the members of the group of instances of programming content for display on the display device in accordance with the playback sequence.
  • 16. The television receiver of claim 14, wherein: determining the group of instances of programming content comprises determining, for each stored instance of programming content of the plurality of stored instances of programming content, whether the stored instance of programming content has been previously viewed by a user of the television receiver; andthe transmitting comprises automatically skipping playback of those members of the group determined to have been previously viewed by the user.
  • 17. The television receiver of claim 13, wherein the operations further comprise: receiving a set of instructions from the content provider; anddetermining the predefined recording parameters from the set of instructions.
  • 18. The television receiver of claim 13, wherein the operations further comprise: receiving a selection of criteria by the content receiver from a user of the television; anddetermining the respective criteria from the selection of criteria.
  • 19. The television receiver of claim 13, wherein each member of the group meets the group criteria by being associated with a same time slot during which the member of the group was originally presented.
  • 20. The television receiver of claim 13, wherein the at least one of the plurality of instances automatically identified for recording by the content receiver based on comparing predefined recording parameters with criteria received in association with receiving the at least one of the plurality of instances.
CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 15/141,304 which was filed on Apr. 28, 2016, and entitled “Grouping and Presenting Content”, which is a continuation of U.S. patent application Ser. No. 13/292,047, which was filed on Nov. 8, 2011, and entitled “Grouping and Presenting Content,” which claims priority to U.S. Provisional Patent Application No. 61/526,506, which was filed on Aug. 23, 2011, and entitled “Grouping and Presenting Content,” which are incorporated by reference into the present application in their entirety.

US Referenced Citations (384)
Number Name Date Kind
4706121 Young Nov 1987 A
4723246 Weldon, Jr. Feb 1988 A
4802215 Mason Jan 1989 A
5187589 Kono et al. Feb 1993 A
5335277 Harvey et al. Aug 1994 A
5483277 Granger Jan 1996 A
5488658 Hirashima Jan 1996 A
5541738 Mankovitz Jul 1996 A
5608652 Astle Mar 1997 A
5642153 Chaney et al. Jun 1997 A
5682597 Ganek et al. Oct 1997 A
5684969 Ishida Nov 1997 A
5724646 Ganek et al. Mar 1998 A
5805763 Lawler et al. Sep 1998 A
5974218 Nagasaka et al. Oct 1999 A
6049333 LaJoie et al. Apr 2000 A
6263504 Ebisawa Jul 2001 B1
6351474 Robinett et al. Feb 2002 B1
6453115 Boyle Sep 2002 B1
6628891 Vantalon et al. Sep 2003 B1
6687296 Sato et al. Feb 2004 B1
6701528 Arsenault et al. Mar 2004 B1
6728883 Kohashi et al. Apr 2004 B1
6766523 Herley Jul 2004 B2
6771703 Oguz et al. Aug 2004 B1
6798971 Potrebic Sep 2004 B2
6925577 Szucs Aug 2005 B1
6938208 Reichardt Aug 2005 B2
7024676 Klopfenstein Apr 2006 B1
7062048 Livaditis et al. Jun 2006 B2
7409140 Rodriguez et al. Aug 2008 B2
7487529 Orlick Feb 2009 B1
7490169 Ogdon et al. Feb 2009 B1
7493312 Liu et al. Feb 2009 B2
7505081 Eshleman Mar 2009 B2
7533402 Demas et al. May 2009 B2
7542656 Cho et al. Jun 2009 B2
7577751 Vinson et al. Aug 2009 B2
7590993 Hendricks et al. Sep 2009 B1
7684672 Matoba Mar 2010 B2
7715552 Pinder et al. May 2010 B2
7730517 Rey et al. Jun 2010 B1
7739711 Finseth et al. Jun 2010 B2
7760986 Beuque Jul 2010 B2
7804861 Kim Sep 2010 B2
7848618 Potrebic et al. Dec 2010 B2
7856557 Beuque Dec 2010 B2
7925141 Geer et al. Apr 2011 B2
7926078 Arsenault et al. Apr 2011 B2
7929697 McNeely et al. Apr 2011 B2
7962937 Cho et al. Jun 2011 B2
8006268 Sloo Aug 2011 B2
8201194 Wijnands et al. Jun 2012 B2
8321466 Black et al. Nov 2012 B2
8364671 Sinton et al. Jan 2013 B1
8437622 Casagrande May 2013 B2
8447170 Casagrande May 2013 B2
8566873 Sie et al. Oct 2013 B2
8584167 Vanduyn Nov 2013 B2
8606088 Kummer et al. Dec 2013 B2
8627349 Kirby et al. Jan 2014 B2
8660412 Kummer et al. Feb 2014 B2
8763027 Martch Jun 2014 B2
8774608 Kummer et al. Jul 2014 B2
8819722 Kummer et al. Aug 2014 B2
8819761 Minnick Aug 2014 B2
8850476 VanDuyn et al. Sep 2014 B2
8867893 Kirby Oct 2014 B2
8959544 Kummer et al. Feb 2015 B2
8959566 Kummer Feb 2015 B2
8989562 Kummer et al. Mar 2015 B2
8997153 Templeman Mar 2015 B2
9031385 Casagrande et al. May 2015 B2
9043843 Templeman et al. May 2015 B2
9055274 Casagrande Jun 2015 B2
9088763 Martch et al. Jul 2015 B2
9113222 VanDuyn Aug 2015 B2
9177605 Minnick et al. Nov 2015 B2
9177606 Kirby Nov 2015 B2
9185331 Martch et al. Nov 2015 B2
9191694 Casagrande Nov 2015 B2
9202524 Martch et al. Dec 2015 B2
9264779 Kirby et al. Feb 2016 B2
9269397 Casagrande et al. Feb 2016 B2
9349412 Templeman May 2016 B2
9350937 Kummer et al. May 2016 B2
9357159 Martch et al. May 2016 B2
9361940 Minnick Jun 2016 B2
9412413 Martch Aug 2016 B2
9489981 Templeman et al. Nov 2016 B2
9489982 Casagrande et al. Nov 2016 B2
9521440 Kummer et al. Dec 2016 B2
9549213 Templeman et al. Jan 2017 B2
9621946 Kennedy Apr 2017 B2
9628838 Kummer et al. Apr 2017 B2
9635436 Casagrande Apr 2017 B2
9756378 Hardy Sep 2017 B2
9781464 Templeman Oct 2017 B2
9854291 Minnick Dec 2017 B2
9894406 Martch et al. Feb 2018 B2
9918116 Robinson Mar 2018 B2
10171861 Minnick Jan 2019 B2
10231009 Martch et al. Mar 2019 B2
20010028782 Ohno et al. Oct 2001 A1
20010033736 Yap et al. Oct 2001 A1
20010034787 Takao et al. Oct 2001 A1
20010049820 Barton Dec 2001 A1
20020044658 Wasilewski et al. Apr 2002 A1
20020054752 Wood et al. May 2002 A1
20020055343 Stetzler et al. May 2002 A1
20020087979 Dudkiewicz et al. Jul 2002 A1
20020087983 Son et al. Jul 2002 A1
20020092021 Yap et al. Jul 2002 A1
20020095510 Sie et al. Jul 2002 A1
20020097340 Takagi et al. Jul 2002 A1
20020116705 Perlman Aug 2002 A1
20020120925 Logan Aug 2002 A1
20020126221 Link Sep 2002 A1
20020141431 Tripathy Oct 2002 A1
20020144259 Gutta et al. Oct 2002 A1
20020144266 Goldman et al. Oct 2002 A1
20020152299 Traversat et al. Oct 2002 A1
20020164147 Suda Nov 2002 A1
20020168178 Rodriguez et al. Nov 2002 A1
20020174430 Ellis et al. Nov 2002 A1
20020184638 Agnihortri et al. Dec 2002 A1
20020188943 Freeman et al. Dec 2002 A1
20030005454 Rodriguez et al. Jan 2003 A1
20030026423 Unger et al. Feb 2003 A1
20030078930 Surcouf et al. Apr 2003 A1
20030097659 Goldman May 2003 A1
20030110514 West et al. Jun 2003 A1
20030123845 Koda Jul 2003 A1
20030149988 Ellis et al. Aug 2003 A1
20030152360 Mukai et al. Aug 2003 A1
20030156826 Sonoda et al. Aug 2003 A1
20030177492 Kanou Sep 2003 A1
20030177495 Needham et al. Sep 2003 A1
20030200548 Baran et al. Oct 2003 A1
20030208763 McElhatten et al. Nov 2003 A1
20030208767 Williamson et al. Nov 2003 A1
20030226150 Berberet et al. Dec 2003 A1
20040001087 Warmus et al. Jan 2004 A1
20040003118 Brown et al. Jan 2004 A1
20040015992 Hasegawa et al. Jan 2004 A1
20040015999 Carlucci et al. Jan 2004 A1
20040078829 Patel et al. Apr 2004 A1
20040078831 Dietz Apr 2004 A1
20040080672 Kessler et al. Apr 2004 A1
20040103428 Seok et al. May 2004 A1
20040128682 Liga et al. Jul 2004 A1
20040133923 Watson et al. Jul 2004 A1
20040148501 Livaditis et al. Jul 2004 A1
20040162871 Pabla et al. Aug 2004 A1
20040218905 Green et al. Nov 2004 A1
20040242150 Wright et al. Dec 2004 A1
20040268387 Wendling Dec 2004 A1
20050002640 Putterman Jan 2005 A1
20050034171 Benya Feb 2005 A1
20050071877 Navarro Mar 2005 A1
20050083865 Ashley et al. Apr 2005 A1
20050120049 Kanegae et al. Jun 2005 A1
20050125683 Matsuyama et al. Jun 2005 A1
20050144646 Lecrom et al. Jun 2005 A1
20050147383 Ihara Jul 2005 A1
20050180568 Krause Aug 2005 A1
20050229213 Ellis et al. Oct 2005 A1
20050237435 Potrebic et al. Oct 2005 A1
20050267656 Dabrowski Dec 2005 A1
20050271365 Hisatomi Dec 2005 A1
20050273819 Knudson et al. Dec 2005 A1
20050281531 Unmehopa Dec 2005 A1
20060010464 Azami Jan 2006 A1
20060020962 Stark et al. Jan 2006 A1
20060056800 Shimagami et al. Mar 2006 A1
20060075434 Chaney et al. Apr 2006 A1
20060078055 Kanazawa Apr 2006 A1
20060080716 Nishikawa et al. Apr 2006 A1
20060085828 Dureau et al. Apr 2006 A1
20060120523 Kurotaki Jun 2006 A1
20060206819 Tsuji et al. Sep 2006 A1
20060212900 Ismail et al. Sep 2006 A1
20060215993 Yamada Sep 2006 A1
20060257099 Potrebic et al. Nov 2006 A1
20060274208 Pedlow, Jr. Dec 2006 A1
20070016546 De Vorchik et al. Jan 2007 A1
20070019930 Kim Jan 2007 A1
20070039032 Goldey et al. Feb 2007 A1
20070055991 Choi et al. Mar 2007 A1
20070061378 Lee et al. Mar 2007 A1
20070154163 Cordray Jul 2007 A1
20070154172 Watanabe Jul 2007 A1
20070157248 Ellis Jul 2007 A1
20070157253 Ellis et al. Jul 2007 A1
20070165855 Inui Jul 2007 A1
20070183745 White Aug 2007 A1
20070192586 McNeely Aug 2007 A1
20070204288 Candelore Aug 2007 A1
20070234395 Dureau et al. Oct 2007 A1
20070250856 Leavens et al. Oct 2007 A1
20070258596 Kahn et al. Nov 2007 A1
20070299976 Zafar et al. Dec 2007 A1
20070300250 Smith et al. Dec 2007 A1
20080022347 Cohen Jan 2008 A1
20080044158 Kido Feb 2008 A1
20080046929 Cho et al. Feb 2008 A1
20080052743 Moore Feb 2008 A1
20080074547 Ida Mar 2008 A1
20080092164 Agarwal et al. Apr 2008 A1
20080092181 Britt Apr 2008 A1
20080101760 Waller May 2008 A1
20080104534 Park et al. May 2008 A1
20080127253 Zhang et al. May 2008 A1
20080137850 Mamidwar Jun 2008 A1
20080141322 Jang et al. Jun 2008 A1
20080144747 Tomizawa Jun 2008 A1
20080152039 Shah et al. Jun 2008 A1
20080184327 Ellis et al. Jul 2008 A1
20080216119 Pfeffer et al. Sep 2008 A1
20080216136 Pfeffer et al. Sep 2008 A1
20080222678 Burke et al. Sep 2008 A1
20080222681 Kwon Sep 2008 A1
20080271077 Kim et al. Oct 2008 A1
20080273698 Manders et al. Nov 2008 A1
20080273856 Bumgardner Nov 2008 A1
20080276284 Bumgardner et al. Nov 2008 A1
20080288461 Glennon et al. Nov 2008 A1
20080291206 Uchimura et al. Nov 2008 A1
20080298585 Maillard et al. Dec 2008 A1
20080301740 Tsutsui Dec 2008 A1
20080307217 Yukimatsu et al. Dec 2008 A1
20090025027 Craner Jan 2009 A1
20090051579 Inaba et al. Feb 2009 A1
20090067621 Wajs Mar 2009 A9
20090080930 Shinotsuka et al. Mar 2009 A1
20090100466 Migos Apr 2009 A1
20090110367 Fukui Apr 2009 A1
20090129741 Kim May 2009 A1
20090129749 Oyamatsu et al. May 2009 A1
20090136206 Aisu May 2009 A1
20090150941 Riedl et al. Jun 2009 A1
20090158370 Li et al. Jun 2009 A1
20090165057 Miller et al. Jun 2009 A1
20090172722 Kahn et al. Jul 2009 A1
20090178098 Westbrook et al. Jul 2009 A1
20090210912 Cholas et al. Aug 2009 A1
20090235298 Carlberg et al. Sep 2009 A1
20090254962 Hendricks et al. Oct 2009 A1
20090260038 Acton et al. Oct 2009 A1
20090320073 Reisman Dec 2009 A1
20090320084 Azam et al. Dec 2009 A1
20090324203 Wiklof Dec 2009 A1
20100020794 Cholas et al. Jan 2010 A1
20100037282 Iwata et al. Feb 2010 A1
20100043022 Kaftan Feb 2010 A1
20100050225 Bennett Feb 2010 A1
20100086277 Craner Apr 2010 A1
20100095323 Williamson et al. Apr 2010 A1
20100100899 Bradbury et al. Apr 2010 A1
20100115121 Roos et al. May 2010 A1
20100135639 Ellis et al. Jun 2010 A1
20100138865 Rai et al. Jun 2010 A1
20100146581 Erk Jun 2010 A1
20100158479 Craner Jun 2010 A1
20100158480 Jung et al. Jun 2010 A1
20100162285 Cohen et al. Jun 2010 A1
20100169926 Westberg et al. Jul 2010 A1
20100195827 Lee et al. Aug 2010 A1
20100217613 Kelly Aug 2010 A1
20100218208 Holden Aug 2010 A1
20100232604 Eklund, II Sep 2010 A1
20100235862 Adachi Sep 2010 A1
20100239228 Sano Sep 2010 A1
20100242079 Riedl et al. Sep 2010 A1
20100246582 Salinger et al. Sep 2010 A1
20100247067 Gratton Sep 2010 A1
20100251304 Donoghue et al. Sep 2010 A1
20100251305 Kimble et al. Sep 2010 A1
20100254386 Salinger et al. Oct 2010 A1
20100265391 Muramatsu et al. Oct 2010 A1
20100272419 Wang et al. Oct 2010 A1
20100284537 Inbar Nov 2010 A1
20100293583 Loebig et al. Nov 2010 A1
20100299528 Le Floch Nov 2010 A1
20100306401 Gilson Dec 2010 A1
20100313222 Lee et al. Dec 2010 A1
20100319037 Kim Dec 2010 A1
20100329645 Sakamoto Dec 2010 A1
20110001879 Goldey et al. Jan 2011 A1
20110007218 Moran et al. Jan 2011 A1
20110008024 Sasaki et al. Jan 2011 A1
20110043652 King et al. Feb 2011 A1
20110078750 Tam et al. Mar 2011 A1
20110080529 Wong Apr 2011 A1
20110099364 Robyr et al. Apr 2011 A1
20110106744 Becker et al. May 2011 A1
20110131413 Moon et al. Jun 2011 A1
20110138169 Michel Jun 2011 A1
20110138424 Vlot Jun 2011 A1
20110145854 Bacon et al. Jun 2011 A1
20110150429 Kaneko Jun 2011 A1
20110162011 Hassell et al. Jun 2011 A1
20110179453 Poniatowski Jul 2011 A1
20110225616 Ellis Sep 2011 A1
20110235701 Kim Sep 2011 A1
20110239249 Murison et al. Sep 2011 A1
20110255002 Witheiler Oct 2011 A1
20110286719 Woods Nov 2011 A1
20110311045 Candelore et al. Dec 2011 A1
20120183276 Quan et al. Jul 2012 A1
20120195433 Eppolito et al. Aug 2012 A1
20120198317 Eppolito et al. Aug 2012 A1
20120198501 Ruan et al. Aug 2012 A1
20120236933 Saitoh Sep 2012 A1
20120260286 Rothschild Oct 2012 A1
20120278837 Curtis et al. Nov 2012 A1
20120296745 Harper et al. Nov 2012 A1
20120301104 Dove Nov 2012 A1
20120311534 Fox et al. Dec 2012 A1
20120311634 Van Duyn Dec 2012 A1
20120331494 Pontual et al. Dec 2012 A1
20120331505 Chun et al. Dec 2012 A1
20130014146 Bhatia et al. Jan 2013 A1
20130014159 Wiser et al. Jan 2013 A1
20130051555 Martch et al. Feb 2013 A1
20130051758 Kummer et al. Feb 2013 A1
20130051764 Casagrande Feb 2013 A1
20130051766 Martch et al. Feb 2013 A1
20130051773 Casagrande Feb 2013 A1
20130054579 Kennedy Feb 2013 A1
20130055304 Kirby et al. Feb 2013 A1
20130055305 Martch et al. Feb 2013 A1
20130055310 VanDuyn et al. Feb 2013 A1
20130055311 Kirby et al. Feb 2013 A1
20130055314 Martch Feb 2013 A1
20130055333 Kummer Feb 2013 A1
20130081098 Klughart Mar 2013 A1
20130216208 Kummer et al. Aug 2013 A1
20130223814 Casagrande Aug 2013 A1
20130243397 Minnick et al. Sep 2013 A1
20130243398 Templeman et al. Sep 2013 A1
20130243399 Casagrande et al. Sep 2013 A1
20130243401 Casagrande Sep 2013 A1
20130243402 Kummer et al. Sep 2013 A1
20130243403 Martch Sep 2013 A1
20130243405 Templeman et al. Sep 2013 A1
20130243406 Kirby Sep 2013 A1
20130247089 Kummer et al. Sep 2013 A1
20130247090 Kummer et al. Sep 2013 A1
20130247106 Martch et al. Sep 2013 A1
20130247107 Templeman Sep 2013 A1
20130247111 Templeman et al. Sep 2013 A1
20130247115 Minnick Sep 2013 A1
20130298166 Herrington et al. Nov 2013 A1
20130347037 Soroushian Dec 2013 A1
20140047477 VanDuyn Feb 2014 A1
20140050462 Kummer et al. Feb 2014 A1
20140115636 Stuckman Apr 2014 A1
20140126889 Kummer et al. May 2014 A1
20140130094 Kirby et al. May 2014 A1
20140147102 Shartzer et al. May 2014 A1
20140201767 Seiden et al. Jul 2014 A1
20140341377 Kummer et al. Nov 2014 A1
20140344858 Minnick Nov 2014 A1
20140363139 Kirby Dec 2014 A1
20140376884 Lovell Dec 2014 A1
20150040166 Tamura et al. Feb 2015 A1
20150095948 Kummer et al. Apr 2015 A1
20150104146 Higuchi et al. Apr 2015 A1
20150121430 Templeman Apr 2015 A1
20150208119 Casagrande et al. Jul 2015 A1
20150208125 Robinson Jul 2015 A1
20150228305 Templeman et al. Aug 2015 A1
20150245089 Protrebic Aug 2015 A1
20150245113 Casagrande Aug 2015 A1
20150319400 Golyshko Nov 2015 A1
20160073144 Robinson Mar 2016 A1
20160080800 Casagrande Mar 2016 A1
20160105711 Martch et al. Apr 2016 A1
20160134926 Casagrande et al. May 2016 A1
20160198215 Hardy Jul 2016 A1
20160234543 Templeman Aug 2016 A1
20160249089 Minnick Aug 2016 A1
20160323632 Martch et al. Nov 2016 A1
Foreign Referenced Citations (53)
Number Date Country
1595975 Mar 2005 CN
1615017 May 2005 CN
1926793 Mar 2007 CN
101174946 May 2008 CN
101202600 Jun 2008 CN
101310532 Nov 2008 CN
101 404 780 Apr 2009 CN
101969538 Nov 2010 CN
101978690 Feb 2011 CN
0 903 743 Mar 1999 EP
0 973 333 Jan 2000 EP
1 001 631 May 2000 EP
1 168 347 Feb 2002 EP
1372339 Dec 2003 EP
1 447 983 Aug 2004 EP
1 667 452 Jul 2006 EP
1 742 467 Jan 2007 EP
2 018 059 Jan 2009 EP
2 317 767 May 2011 EP
2 357 563 Aug 2011 EP
2 541 929 Jan 2013 EP
2 748 728 Jan 2015 EP
2 826 197 Jan 2015 EP
2 826 238 Jan 2015 EP
2 459 705 Nov 2009 GB
9740CHENP2013 Sep 2014 IN
7408CHENP2014 Jan 2016 IN
9493CHENP2013 Jun 2016 IN
2007 116525 May 2007 JP
2010165058 Jul 2010 JP
9812872 Mar 1998 WO
0124532 Apr 2001 WO
0241625 May 2002 WO
2004057610 Aug 2004 WO
2007047410 Apr 2007 WO
2008010118 Jan 2008 WO
2008010689 Jan 2008 WO
2008060486 May 2008 WO
2011081729 Jul 2011 WO
2011027236 Oct 2011 WO
2012003693 Jan 2012 WO
2013028824 Feb 2013 WO
2013028829 Feb 2013 WO
2013028835 Feb 2013 WO
2013138606 Sep 2013 WO
2013138608 Sep 2013 WO
2013138610 Sep 2013 WO
2013138638 Sep 2013 WO
2013138689 Sep 2013 WO
2013138740 Sep 2013 WO
2013028814 May 2014 WO
2016066443 May 2016 WO
2016111817 Jul 2016 WO
Non-Patent Literature Citations (229)
Entry
Canadian Office Action for 2,838,750 dated Feb. 7, 2020, all pages.
Search Report dated Oct. 29, 2019 for BR112013032860-6, all pages.
Publication of BR112013032860-6 dated Oct. 29, 2019, 2 pages.
Office Action for EP 128254745 dated Aug. 4, 2017, all pages.
Wikipedia: “MPEG-2 Transmission”, Internet Citation, Jan. 31, 2001, pp. 1-9, XP002715999, Retrieved from the Internet: URL: http://www.erg.abdn.ac.uk/future-net/digital-video/mpeg2-trans.html.
International Search Report and Written Opinion of PCT/US2012/51992 dated Nov. 2, 2012, 15 pages.
International Search Report and Written Opinion of PCT/US2012/51987 dated Oct. 23, 2012, 20 pages.
International Search Report and Written Opinion of PCT/US2012/051984 dated Nov. 5, 2012, 13 pages.
International Search Report and Written Opinion of PCT/US2012/52002 dated Oct. 16, 2012, 17 pages.
International Search Report and Written Opinion of PCT/US2013/031432 dated May 28, 2013, 10 pages.
International Preliminary Report on Patentability for PCT/US2013/031432 dated Sep. 16, 2014, 9 pages.
International Search Report and Written Opinion of PCT/US2013/031445 dated May 24, 2013, 11 pages.
International Preliminary Report on Patentability for PCT/US2013/031445 dated Sep. 16, 2014, 10 pages.
International Preliminary Report on Patentability for PCT/US2012/052002 dated Apr. 17, 2014, 10 pages.
International Search Report and Written Opinion of PCT/US2012/51964 dated Nov. 2, 2012, 13 pages.
International Search Report and Written Opinion of PCT/US2015/065934 dated Apr. 8, 2016, all pages.
International Prelminary Report on Patentability for PCT/US2015/065934 dated Jul. 11, 2017, all pages.
International Search Report and Written Opinion of PCT/EP2015/073937 dated Apr. 15, 2016, all pages.
International Search Report and Written Opinion of PCT/US2012/052011 dated Dec. 17, 2012, 44 pages.
International Preliminary Report on Patentability, PCT/US2012/052011, dated Mar. 6, 2014, 6 pages.
International Preliminary Report on Patentability, PCT/US2012/051984, dated Mar. 6, 2014, 8 pages.
International Preliminary Report on Patentability, PCT/US2012/051964, dated Apr. 10, 2014, 7 pages.
International Preliminary Report on Patentability, PCT/US2012/051992, dated Apr. 3, 2014, 7 pages.
International Preliminary Report on Patentability, PCT/US2012/051987, dated Mar. 6, 2014, 7 pages.
Hee-Yong Kim et al., “DCT Domain Filter for ATV Down Conversion”, Consumer Electronics, 1997. Digest of Technical Papers. ICCE., International Conference ON, IEEE, Jun. 11, 1997, pp. 142-143, XP032381904, DOI: 10.1109/ICCE. 1997.625904, ISBN: 978-0-7803-3734-3.
Author Unknown, “Move Networks is Delivering the Next Generation of Television,” Move Networks, 2010, obtained online at http://movenetworks.com/, 2 pages.
Design and implementation of a multi-stream cableCARD with a high-speed DVB-common descrambler; Joonyoung Jung, Ohyung Kwon, Sooin Lee; In proceeding of: Proceedings of the 14th ACM International Conference on Multimedia, Santa Barbara, CA, USA, Oct. 23-27, 2006, 4 pages.
Anonymous: “The Angry Technician's Guide to streaming Freeview via VLC, you Idiots / The Angry Technician”, Jun. 24, 2010, XP055388589, Retrieved from the internet: URL: https://angrytechnician.wordpress.com/2010/06/24/the-angry-technicians-guide-to-streaming-freeview-via-vlc-you-idiots/ [retrieved on Jul. 6, 2017], 14 pages.
Anonymous: “Documentation: Playback—VideoLAN Wiki”, Dec. 25, 2010, XP055388595, Retrieved from the Internet: URL:https://wiki.videolan.org/index.php? Title=Documentation:Playback&oldid=18460 [retrieved on Jul. 6, 2017], 3 pages.
Anonymous: “How to Watch DVB-T With VLC Media Player”, Jan. 25, 2009, XP055388602, Retrieved from the Internet: URL: http://www.izitips.com/software/how-to-watch-dvb-t-with-vlc-media-player/ [retrieved on Jul. 6, 2017], 3 pages.
Anonymous: “News—VideoLAN”, Jul. 15, 2011, XP055388604, Retreived from the Internet: URL: http://www.videolan.org/news.html#news-2011-07-15 [retrieved on Jul. 6, 2017], 69 pages.
Office Action for EP 12825147.7, 7 pages.
Office Action for EP 13 192 169.4 dated Mar. 29, 2016, all pages.
U.S. Appl. No. 13/786,915, filed Mar. 6, 2013, Non Final Rejection dated Oct. 15, 2015, 59 pages.
U.S. Appl. No. 13/786,915, filed Mar. 6, 2013, Final Rejection dated May 12, 2016, 27 pages.
U.S. Appl. No. 13/786,915, filed Mar. 6, 2013, Notice of Allowance dated Jul. 19, 2016, all pages.
U.S. Appl. No. 14/757,606, filed Dec. 23, 2015, Non Final Rejection dated Mar. 24, 2016, 33 pages.
U.S. Appl. No. 14/757,606, filed Dec. 23, 2015, Notice of Allowance dated Jul. 18, 2016, all pages.
U.S. Appl. No. 14/340,190, filed Jul. 24, 2014, Non-Final Rejection dated Aug. 31, 2015, 74 pages.
U.S. Appl. No. 14/340,190, filed Jul. 24, 2014, Final Rejection dated Feb. 19, 2016, 54 pages.
U.S. Appl. No. 14/340,190, filed Jul. 24, 2014, Notice of Allowance dated Aug. 22, 2016, all pages.
U.S. Appl. No. 14/154,887, filed Jan. 14, 2014 Non-Final Rejection dated Jul. 17, 2015, 33 pages.
U.S. Appl. No. 14/154,887, filed Jan. 14, 2014 Notice of Allowance dated Jan. 21, 2016, 26 pages.
U.S. Appl. No. 14/467,959, filed Aug. 25, 2014 Notice of Allowance dated Jun. 22, 2015, 36 pages.
U.S. Appl. No. 13/888,012, filed May 6, 2013 Non-Final Rejection dated Apr. 6, 2015, 36 pages.
U.S. Appl. No. 13/888,012, filed May 6, 2013 Notice of Allowance dated Jul. 14, 2015, 18 pages.
U.S. Appl. No. 13/856,752, filed Apr. 4, 2013 Non Final Office Action dated Nov. 5, 2014, 34 pages.
U.S. Appl. No. 13/856,752, filed Apr. 4, 2013 Notice of Allowance dated Feb. 10, 2015, 20 pages.
U.S. Appl. No. 13/757,168, filed Feb. 1, 2013 Notice of Allowance dated Oct. 14, 2014, 28 pages.
U.S. Appl. No. 13/757,168, filed Feb. 1, 2013, Non Final Office Action dated Jun. 4, 2014, 23 pages.
U.S. Appl. No. 13/799,604, filed Mar. 13, 2013, Notice of Allowance dated Jul. 24, 2015, 34 pages.
U.S. Appl. No. 13/799,604, filed Mar. 13, 2013, Notice of Allowance dated May 29, 2015, 46 pages.
U.S. Appl. No. 13/799,604, filed Mar. 13, 2013, Final Office Action dated Jan. 14, 2015, 36 pages.
U.S. Appl. No. 13/799,604, filed Mar. 13, 2013, Non Final Office Action dated Jun. 6, 2014, 24 pages.
U.S. Appl. No. 13/149,852, filed May 31, 2011, Non-Final Office Action dated Dec. 12, 2012, 9 pages.
U.S. Appl. No. 13/149,852, filed May 31, 2011, Final Office Action dated Mar. 26, 2013, 13 pages.
U.S. Appl. No. 13/149,852, filed May 31, 2011, Notice of Allowance dated Jul. 11, 2013, 13 pages.
U.S. Appl. No. 13/286,157, filed Oct. 31, 2011, Non-Final Office Action dated Jan. 17, 2013, 20 pages.
U.S. Appl. No. 13/286,157, filed Oct. 31, 2011, Non-Final Office Action dated Jul. 25, 2013, 49 pages.
U.S. Appl. No. 13/286,157, filed Oct. 31, 2011, Notice of Allowance dated Feb. 3, 2014, 81 pages.
U.S. Appl. No. 13/215,702, filed Aug. 23, 2011, Notice of Allowance dated Feb. 11, 2013, 13 pages.
U.S. Appl. No. 13/288,002, filed Nov. 2, 2011, Non-final Office Action dated Sep. 26, 2013, 15 pages.
U.S. Appl. No. 13/288,002, filed Nov. 2, 2011, Final Office Action dated Mar. 27, 2014, 20 pages.
U.S. Appl. No. 13/288,002, filed Nov. 2, 2011 Non Final Rejection dated Jul. 28, 2015, 29 pages.
U.S. Appl. No. 13/288,002, filed Nov. 2, 2011 Final Rejection dated Jan. 13, 2016, 22 pages.
U.S. Appl. No. 13/302,852, filed Nov. 22, 2011 Non-Final Rejection dated May 23, 2013, 19 pages.
U.S. Appl. No. 13/302,852, filed Nov. 22, 2011, Notice of Allowance dated Jun. 19, 2015, 26 pages.
U.S. Appl. No. 13/302,852, filed Nov. 22, 2011, Final Rejection dated Dec. 9, 2013, 23 pages.
U.S. Appl. No. 13/302,852, filed Nov. 22, 2011, Non-Final Rejection dated Sep. 2, 2014, 28 pages.
U.S. Appl. No. 13/302,852, filed Nov. 22, 2011, Final Rejection dated Mar. 30, 2015, 29 pages.
The Notice of Allowance by the Mexican Institute of Industrial Property for Mexican Patent Application No. MX/a/2013/014907 dated Feb. 20, 2015 is not translated into English, 1 page.
U.S. Appl. No. 13/324,831, filed Dec. 13, 2011, Non-Final Office Action dated Feb. 28, 2013, 23 pages.
U.S. Appl. No. 13/324,831, filed Dec. 13, 2011, Notice of Allowance dated Sep. 4, 2013, 22 pages.
U.S. Appl. No. 13/292,047, filed Nov. 8, 2011, Non-Final Office Action dated Jan. 18, 2013, 17 pages.
U.S. Appl. No. 13/292,047, filed Nov. 8, 2011, Final Office Action dated Aug. 19, 2013, 17 pages.
U.S. Appl. No. 13/292,047, filed Nov. 8, 2011 Final Office Action dated Jan. 13, 2015, 22 pages.
U.S. Appl. No. 13/292,047, filed Nov. 8, 2011 Non-Final Office Action dated Jul. 7, 2015, 28 pages.
U.S. Appl. No. 13/292,047, filed Nov. 8, 2011 Notice of Allowance dated Jan. 29, 2016, 45 pages.
U.S. Appl. No. 13/614,899, filed Sep. 13, 2012, Non-Final Office Action dated Feb. 5, 2013, 17 pages.
U.S. Appl. No. 13/614,899, filed Sep. 13, 2012, Non-Final Office Action dated May 20, 2014, 25 pages.
U.S. Appl. No. 13/614,899, filed Sep. 13, 2012, Non-Final Office Action dated Sep. 17, 2013, 17 pages.
U.S. Appl. No. 13/614,899, filed Sep. 13, 2012, Final Office Action dated Mar. 17, 2014, 41 pages.
U.S. Appl. No. 13/614,899, filed Sep. 13, 2012, Notice of Allowance dated Mar. 13, 2015, 35 pages.
U.S. Appl. No. 13/291,014, filed Nov. 7, 2011, Non-Final Office Action dated Mar. 29, 2013, 21 pages.
U.S. Appl. No. 13/291,014, filed Nov. 7, 2011, Notice of Allowance dated Aug. 7, 2013, 16 pages.
U.S. Appl. No. 13/215,598, filed Aug. 23, 2011, Non-Final Office Action dated Jun. 20, 2013, 15 pages.
U.S. Appl. No. 13/215,598, filed Aug. 23, 2011, Final Office Action dated Nov. 21, 2013, 23 pages.
U.S. Appl. No. 13/215,598, filed Aug. 23, 2011, Non-Final Office Action dated Feb. 6, 2014, 12 pages.
U.S. Appl. No. 13/215,598, filed Aug. 23, 2011 Non-Final Office Action dated Nov. 25, 2014, 18 pages.
U.S. Appl. No. 13/215,598, filed Aug. 23, 2011 Final Office Action dated Jul. 2, 2014, 22 pages.
U.S. Appl. No. 13/215,598, filed Aug. 23, 2011 Final Office Action dated May 5, 2015, 17 pages.
U.S. Appl. No. 13/215,598, filed Aug. 23, 2011 Non Final Office Action dated Dec. 15, 2015, all pages.
U.S. Appl. No. 13/215,598, filed Aug. 23, 2011 Notice of Allowance dated May 24, 2016, all pages.
U.S. Appl. No. 13/215,655, filed Aug. 23, 2011, Non-Final Office Action dated Sep. 6, 2013, 27 pages.
U.S. Appl. No. 13/215,655, filed Aug. 23, 2011, Final Office Action dated Dec. 18, 2013, 20 pages.
U.S. Appl. No. 13/215,916, filed Aug. 23, 2011, Notice of Allowance dated Jan. 4, 2013, 10 pages.
U.S. Appl. No. 13/294,005, filed Nov. 11, 2011 Notice of Allowance dated Oct. 31, 2014, 24 pages.
U.S. Appl. No. 13/294,005, filed Nov. 11, 2011 Non-Final Office Action dated May 20, 2014, 33 pages.
U.S. Appl. No. 13/294,005, filed Nov. 11, 2011, Non-Final Office Action dated Aug. 14, 2013, 32 pages.
U.S. Appl. No. 13/294,005, filed Nov. 11, 2011, Final Office Action dated Jan. 3, 2014, 29 pages.
U.S. Appl. No. 13/592,976, filed Aug. 23, 2012, Notice of Allowance dated Oct. 7, 2013, 18 pages.
U.S. Appl. No. 13/797,173, filed Mar. 12, 2013 Notice of Allowance dated Nov. 24, 2014, 37 pages.
U.S. Appl. No. 13/797,173, filed Mar. 12, 2013 Notice of Allowance dated Feb. 26, 2015, 19 pages.
U.S. Appl. No. 13/797,173, filed Mar. 12, 2013, Non Final Office Action dated May 15, 2014, 28 pages.
U.S. Appl. No. 13/799,653, filed Mar. 13, 2013 Notice of Allowance dated Nov. 26, 2014, 32 pages.
U.S. Appl. No. 13/799,653, filed Mar. 13, 2013, Non Final Office Action dated May 8, 2014, 24 pages.
U.S. Appl. No. 13/801,968, filed Mar. 13, 2013 Non Final Office Action dated May 21, 2015, 49 pages.
U.S. Appl. No. 13/801,968, filed Mar. 13, 2013 Final Office Action dated Nov. 19, 2015, all pages.
U.S. Appl. No. 13/801,968, filed Mar. 13, 2013 Notice of Allowance dated Apr. 7, 2016, 33 pages.
U.S. Appl. No. 13/829,350, filed Mar. 14, 2013, Non Final Office Action dated Feb. 28, 2014, 29 pages.
U.S. Appl. No. 13/829,350, filed Mar. 14, 2013 Non Final Office Action dated Jul. 29, 2014, 24 pages.
U.S. Appl. No. 13/829,350, filed Mar. 14, 2013 Final Office Action dated Jan. 23, 2015, 18 pages.
U.S. Appl. No. 13/829,350, filed Mar. 14, 2013 Notice of Allowance dated Jul. 24, 2015, 29 pages.
U.S. Appl. No. 13/828,001, filed Mar. 14, 2013, Notice of Allowance dated Apr. 25, 2014, 43 pages.
U.S. Appl. No. 13/799,719, filed Mar. 13, 2013, Non Final Office Action dated Oct. 25, 2013, 79 pages.
U.S. Appl. No. 13/799,719, filed Mar. 13, 2013, Notice of Allowance dated Apr. 23, 2014, 141 pages.
U.S. Appl. No. 13/801,994, Non Final Office Action dated Oct. 7, 2015, 55 pages.
U.S. Appl. No. 13/801,994, Final Office Action dated May 4, 2016, 37 pages.
U.S. Appl. No. 14/589,090, Notice of Allowance dated Feb. 9, 2016, 47 pages.
U.S. Appl. No. 14/860,366, Non-Final Office Action dated Mar. 24, 2017, all pages.
U.S. Appl. No. 14/944,758, Non-Final Office Action dated Jan. 25, 2017, all pages.
U.S. Appl. No. 15/141,304, Non-Final Office Action dated Feb. 28, 2017, all pages.
U.S. Appl. No. 15/141,304, Final Rejection dated Oct. 18, 2017, all pages.
U.S. Appl. No. 15/141,304, Non-Final Office Action dated Apr. 6, 2018, all pages.
U.S. Appl. No. 15/143,999, filed May 2, 2016, Non-Final Rejection dated Apr. 20, 2017, all pages.
U.S. Appl. No. 15/143,999, filed May 2, 2016, Notice of Allowance dated Aug. 25, 2017, all pages.
U.S. Appl. No. 15/815,452, filed Nov. 16, 2017 Non-Final Rejection dated Mar. 13, 2018, all pages.
U.S. Appl. No. 14/591,549, Non Final Office Action dated Dec. 31, 2015, 19 pages.
U.S. Appl. No. 14/591,549, Final Office Action dated Jun. 30, 2016, all pages.
U.S. Appl. No. 14/591,549, Non Final Office Action dated Dec. 14, 2016, all pages.
U.S. Appl. No. 14/064,423, filed Oct. 28, 2013, Non-Final Office Action dated Dec. 20, 2013, 18 pages.
U.S. Appl. No. 14/064,423, filed Oct. 28, 2013, Notice of Allowance dated Mar. 4, 2013, 37 pages.
U.S. Appl. No. 14/060,388, filed Oct. 22, 2013, Notice of Allowance dated Apr. 13, 2015, 44 pages.
U.S. Appl. No. 13/793,636, filed Mar. 11, 2013, Non-Final Office Action dated Sep. 29, 2014, 27 pages.
U.S. Appl. No. 13/793,636, filed Mar. 11, 2013, Notice of Allowance dated Jan. 28, 2015, 43 pages.
International Search Report of PCT/KR2007/003521 dated Oct. 23, 2007, 22 pages.
International Search Report of PCT/IB2003/005737 dated Mar. 2, 2004, 21 pages.
Jensen, Craig, “Fragmentation: the condition, the cause, the cure” ′Online!, Executive Software International, 1994; ISBN: 0964004909; retrieved from Internet: <URL: www.executive.com/fragbook/fragbook.htm> Chapter: “How a disk works”, Section: “The original problem”. Retrieved on Jan. 9, 2014, 70 pages.
U.S. Appl. No. 14/095,860, filed Dec. 3, 2013 Non-Final Office Action dated Dec. 26, 2014, 45 pages.
U.S. Appl. No. 14/095,860, filed Dec. 3, 2013 Final Office Action dated May 1, 2015, 18 pages.
U.S. Appl. No. 14/095,860, filed Dec. 3, 2013 Notice of Allowance dated Jul. 13, 2015, 31 pages.
U.S. Appl. No. 14/095,860, filed Dec. 3, 2013 Notice of Allowance dated Oct. 19, 2015, 14 pages.
U.S. Appl. No. 14/695,188 Non Final Office Action dated Dec. 30, 2016, all pages.
U.S. Appl. No. 14/695,188 Final Office Action dated Jul. 28, 2017, all pages.
U.S. Appl. No. 14/338,114, filed Jul. 22, 2014 Non-Final Office Action dated Sep. 30, 2015, all pages.
U.S. Appl. No. 14/338,114, filed Jul. 22, 2014 Notice of Allowance dated Feb. 3, 2016, all pages.
U.S. Appl. No. 14/529,989, filed Oct. 31, 2014 Non-Final Office Action dated Nov. 4, 2015, all pages.
U.S. Appl. No. 14/529,989, filed Oct. 31, 2014, Final Rejection dated May 6, 2016, 27 pages.
U.S. Appl. No. 13/795,914, filed Mar. 6, 2013 Notice of Allowance dated Jul. 21, 2014, 13 pages.
U.S. Appl. No. 13/795,914, filed Mar. 6, 2013 Final Office Action dated Apr. 3, 2014, 17 pages.
U.S. Appl. No. 13/795,914, filed Mar. 6, 2013, Non-Final Office Action dated Oct. 11, 2013, 17 pages.
U.S. Appl. No. 13/800,477, filed Mar. 13, 2013 Non-Final Office Action dated Sep. 11, 2014, 34 pages.
U.S. Appl. No. 13/800,477, filed Mar. 13, 2013 Notice of Allowance dated Feb. 18, 2015, 18 pages.
U.S. Appl. No. 14/043,617, filed Oct. 1, 2013 Non-Final Office Action dated Jan. 5, 2015, 45 pages.
U.S. Appl. No. 14/043,617, filed Oct. 1, 2013 Final Office Action dated Jul. 16, 2015, 45 pages.
U.S. Appl. No. 14/043,617, filed Oct. 1, 2013, Final Office Action dated May 6, 2016, 56 pages.
U.S. Appl. No. 14/043,617, filed Oct. 1, 2013, Non-Final Office Action dated Sep. 29, 2016, all pages.
U.S. Appl. No. 14/043,617, filed Oct. 1, 2013, Notice of Allowance dated Dec. 23, 2016, all pages.
U.S. Appl. No. 14/043,617, filed Oct. 1, 2013 Non-Final Office Action dated Oct. 23, 2015, all pages.
U.S. Appl. No. 14/676,137, filed Apr. 1, 2015 Notice of Allowance dated Sep. 28, 2015, 35 pages.
U.S. Appl. No. 15/131,868, filed Apr. 18, 2016 Non-Final Office Action dated Jan. 13, 2017, all pages.
U.S. Appl. No. 15/131,868, filed Apr. 18, 2016 Notice of Allowance dated Jun. 16, 2017, all pages.
International Preliminary Report on Patentability for PCT/US2013/032176 dated Sep. 25, 2014, 7 pages.
International Search Report and Written Opinion of PCT/US2013/32176 dated Jun. 25, 2013, 15 pages.
International Search Report and Written Opinion of PCT/US2013/031565 dated May 31, 2013, 82 pages.
International Preliminary Report on Patentability for PCT/US2013/031565 dated Sep. 16, 2014, 18 pages.
International Preliminary Report on Patentability for PCT/US2013/031915 dated Sep. 16, 2014, 5 pages.
International Search Report and Written Opinion of PCT/US2013/031915 dated Jun. 3, 2013, 7 pages.
International Search Report and Written Opinion of PCT/US2013/031440 dated May 30, 2013, 14 pages.
European Search Report for EP 12825653 dated Mar. 11, 2015, 7 pages.
Extended European Search Report for EP 12825080 dated Sep. 11, 2014, 10 pages.
Extended European Search Report for EP 12825521 dated Nov. 24, 2014, 7 pages.
Extended European Search Report for EP 12825474 dated Jan. 7, 2015, 6 pages.
Extended European Search Report for EP 12825430 dated Feb. 3, 2015, 9 pages.
Supplementary European Search Report for Application No. EP 12825147 dated Mar. 27, 2015, 9 pages.
Notice of Publication for BR 11 2013 032035-4 dated Dec. 20, 2016, 1 page.
Notice of Publication for BR 11 2013 032380-9 dated Jan. 3, 2017, 1 page.
Notice of Publication for BR 11 2013 032860-6 dated Jan. 24, 2017, 1 page.
Notice of Publication for BR 11 2013 032377-9 dated Jan. 3, 2017, 1 page.
Notice of Publication for BR 11 2014 020064-5 A2 dated Jul. 20, 2017, 1 page.
Office Action for European Application No. 12825147 dated Mar. 7, 2016, all pages.
Office Action for European Application No. 12825147 dated Aug. 23, 2016, all pages.
First Office Action and Search Report for CN Appln No. 201380014409.2 dated Oct. 9, 2016, all pages.
Second Office Action for CN Appln No. 201380014409.2 dated Jun. 7, 2017, all pages.
Supplementary European Search Report for EP 13761291.7 dated Jul. 9, 2015, 8 pages.
Office Action dated Nov. 29, 2016 for EP 13 761 291.7, all pages.
Evans, Brent: “GeekTonic: Jan. 25, 2009-Feb. 1, 2009”, Jan. 31, 2009, SP55322053, Retreived from the Internet: URL: http://www.geektonic.com/2009_01_25_archive.html [retrieved on Nov. 23, 2016], 26 pages.
McCann, John, “EE TV set top takes aim at Sky, Virgin Media and YouView,” dated Oct. 8, 2014, 5 pages. Retrieved on Oct. 13, 2014 from http://www.techradar.com/news/television/ee-tv-set-top-box-takes-aim-at-sky-virgin-media-and-youview-1268223.
Supplementary European Search Report for EP 13761427 dated Oct. 19, 2015, all pages.
Extended European Search Report for EP 13760237.1, 8 pages.
Author Unknown, “EE Launches home TV service in UK,” dated Oct. 8, 2014, 3 pages. Retrieved on Oct. 13, 2014 from http://www.bbc.com/news/technology-29535279.
Author Unknown, Digital Video Broadcasting (DVB); Content Protection and Copy Management (DVB-CPCM); Part 3: CPCM Usage State Information; European Broadcasting Union Union Europa de Radio-Television, ETSI TS 102 825-3 V1.1.1 (Jul. 2008), XP014042034, 28 pages.
First Office Action and Search Report from the State Intellectual Property Office (SIPO) for CN 201280031150.8, dated Aug. 3, 2016, 10 pages.
Author Unknown, “Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB systems,” ETSI EN 300 468 V1.1 (Jan. 2013), 172 pages.
Decision to Grant from the State Intellectual Property Office (SIPO) for CN 201280031434.7, dated May 12, 2016, all pages.
Author Unknown, “Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB systems,” ETSI EN 300 468 V1.9.1 (Mar. 2009), 116 pages.
First Office Action issued by State Intellectual Property Office (SIPO) for CN 201280028697.2, dated Dec. 16, 2015, 11 pages.
Second Office Action issued by State Intellectual Property Office for CN 201280028697.2, dated Jul. 8, 2016, all pages.
Third Office Action issued by State Intellectual Property Office for CN 201280028697.2, dated Dec. 29, 2016, all pages.
Notice of Allowance received for Mexican Patent Appln. MX/a/2013/014991, dated Dec. 9, 2015, 1 page.
The second Office Action dated Feb. 26, 2015 for Mexican Pat. Appln. No. MX/a/2013/014217 is not translated into English, 3 pages.
The Office Action dated Nov. 7, 2014 for Mexican Patent Application No. MX/a/2013/014907 is not translated into English, 3 pages.
The Office Action dated Jan. 23, 2015 for Mexican Patent Application No. MX/a/2013/014671 is not translated into English, 3 pages.
Notice of Allowance dated Dec. 16, 2015 for Mexican Patent Application No. MX/a/2014/009919, 1 page.
First Office Action and Search Report for CN Appln No. 201280030476.9 dated Aug. 9, 2016, all pages.
The Office Action dated Nov. 6, 2014 for Mexican Patent Application No. MX/a/2013/014677 is not translated into English, 2 pages.
The Notice of Allowance by the Mexican Institute of Industrial Property for Mexican Patent Application No. MX/a/2013/014677 dated Mar. 19, 2015 is not translated into English, 1 page.
Office Action dated May 18, 2015 for Mexican Patent Application No. MX/a/2014/009776, 2 pages.
Williams, Christopher, “EE to launch TV set-top box,” dated Oct. 7, 2014, 2 pages. Retrieved on Oct. 13, 2014 from http://www.telegraph.co.uk/finance/newsbysector/mediatechnologyandtelecoms/telecoms/11147319/EE-to-launch-TV-set-top-box.html.
Author Unknown, “EE TV It's simply great television,” Accessed on Oct. 13, 2014, 11 pages. Retrieved from https//ee.co.uk/ee-and-me/ee-tv.
Notice of Allowance dated Jul. 21, 2016 for Mexican Patent Application No. MX/a/2015/10334, 1 page.
Office Action dated Jul. 31, 2015 for Mexican Patent Application No. MX/a/2014/009928, 2 pages.
Notice of Allowance dated Jan. 15, 2016 for Mexican Patent Application No. MX/a/2014/009928, 1 page.
Office Action dated Jul. 31, 2015 for Mexican Patent Application No. MX/a/2014/009919, 2 pages.
Notice of Allowance dated Jun. 3, 2016 for Mexican Patent Application No. MX/a/2015/009985, 1 page.
Notice of Allowance dated Jun. 6, 2016 for Mexican Patent Application No. MX/a/2015/015383, 1 page.
Publication of Brazil appln No. BR 11 2013 031100-2 on Jun. 6, 2017, 1 page.
First Office Action and Search Report from the State Intellectual Property Office (SIPO) for CN 201280031434.7, dated Jul. 17, 2015, 12 pages.
Decision to Grant from the State Intellectual Property Office (SIPO) for CN 201280031150.8 dated Apr. 18, 2018, all pages.
Office Action for Canadian Appln No. 2,838,750 dated Apr. 16, 2018, all pages.
U.S. Appl. No. 14/880,934, filed Oct. 12, 2015, Non-Final Rejection dated Mar. 7, 2018, all pages.
U.S. Appl. No. 14/880,934, filed Oct. 12, 2015, Notice of Allowance dated Jul. 2, 2018, all pages.
Office Action for Canadian Appln No. 2,838,750 dated Mar. 19, 2019, all pages.
Office Action for CA 2,865,746, all pages.
Office Action for CA 2,865,852, all pages.
Office Action for CA 2,838,264, all pages.
Office Action for CA 2,837,733, all pages.
Office Action for EP 13761427 dated Mar. 2, 2018, all pages.
Office Action for IN 9740/CHEN/2013 dated Nov. 5, 2018, all pages.
Related Publications (1)
Number Date Country
20190158911 A1 May 2019 US
Provisional Applications (1)
Number Date Country
61526506 Aug 2011 US
Continuations (2)
Number Date Country
Parent 15141304 Apr 2016 US
Child 16254613 US
Parent 13292047 Nov 2011 US
Child 15141304 US