The advent of the DVR (Digital Video Recorder) and the availability of high-capacity and affordable computer-readable storage devices have made available many possibilities to television programming service providers and viewers alike. In recent years, television viewers have come to expect the ability to customize and manage the recording of television programming via their television receivers.
This Summary does not in any way limit the scope of the claimed subject matter.
In an aspect, a computer-implemented method is disclosed. The method may include determining a current status of each one of a plurality of tuners of a television receiver in response to receiving a request to allocate a tuner of the television receiver for the recording of a particular broadcast program. The method may include assigning a ranking to each one of the plurality of tuners based on an associated determined status. The method may include generating a listing based on the ranking, wherein when selected a particular tuner of ranking greater than each of other ones of the plurality of tuners is allocated for the recording of the particular broadcast program.
In an aspect, a system including one or more processors and a memory communicatively coupled with and readable by the one or more processors is disclosed. The memory may have stored therein processor-readable instructions which, when executed by the one or more processors, cause the one or more processors to determine a current status of each one of a plurality of tuners of a television receiver based on a request to allocate a tuner of the television receiver for the recording of a particular broadcast program. The memory may have stored therein processor-readable instructions which, when executed by the one or more processors, cause the one or more processors to assign a ranking to each one of the plurality of tuners based on an associated determined status. The memory may have stored therein processor-readable instructions which, when executed by the one or more processors, cause the one or more processors to generate a listing based on the ranking, wherein when selected a particular tuner of ranking greater than each of other ones of the plurality of tuners is allocated for the recording of the particular broadcast program.
In an aspect, a non-transitory processor-readable medium comprising processor-readable instructions is disclosed. The processor-readable instructions may be configured to cause one or more processors to, based on a request to allocate a tuner of a television receiver for the recording of a particular broadcast program, determine a current status of each one of a plurality of tuners of the television receiver. The processor-readable instructions may be configured to cause one or more processors to assign a ranking to each one of the plurality of tuners based on an associated determined status. The processor-readable instructions may be configured to cause one or more processors to generate a listing based on the ranking, wherein when selected a particular tuner of ranking greater than each of other ones of the plurality of tuners is allocated for the recording of the particular broadcast program.
A further understanding of the nature and advantages of various embodiments may be realized by reference to the following figures. In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. When only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.
The present disclosure is directed to or towards the automated selection of a particular television receiver tuner that is to be used for the recording of particular media content. Although described in the context of a satellite-based content distribution system, the various aspects of the present disclosure may generally be applicable to any scenario in which it is desirable to maximize or optimize the allocation of computing system or device resources. For example, referring now to
The method 100 may include receiving (module 102), by the television receiver, an indication of an upcoming or imminent activation of a scheduled program recording timer. For example, the television receiver may receive a warning signal at a particular time prior to activation of the recording timer. The particular time may be predetermined and configurable. For example, the television receiver may receive the warning signal at time of 0.5 seconds, or 2 seconds, or 5 seconds, or 10 seconds, etc., prior to activation of the recording timer. In general, the recording timer may be defined or configured to implement, upon activation, a recording of particular broadcast programming at a predetermined date and time. For example, the timer may be configured to instantiate the recording of a “Show S1” that is scheduled to appear on a channel “2012” during a particular time period “9-10 PM” of a particular day (see e.g.,
The method 100 may further include determining (module 104), by the television receiver in response to receiving the indication, a current status of each of the plurality of tuners of the television receiver. In general, each of the plurality of tuners may be in one of an inactive state and an active state. A tuner in an inactive state may, for example, refer to a tuner that is not currently in-use. A current status of an inactive tuner may be defined as “inactive.” A tuner in an active state may, for example, refer to a tuner that is currently being used for recording, but will be no longer be recording at a “start” time associated with the recording timer and thus may be available for recording of the particular broadcast programming. A current status of an active tuner in this scenario may be defined as “active; recording; assignable.” In another example, a tuner in an active state may, for example, refer to a tuner that is currently being used to select particular live programming for presentation by a display device. A current status of an active tuner in this scenario may be defined as “active; live.” Other embodiments are possible.
An example sequence of steps to resolve or determine a current status of each of a plurality of tuners of a television receiver is described in further detail below in connection with
The method 100 may further include generating (module 106), by the television receiver upon determining a current status of each of the plurality of tuners, a listing that ranks each of the plurality of tuners against each other based on respective “current” status. For example, the “active; recording; assignable” tuner status may be predefined as having a ranking or priority greater than the “active; live” tuner status, which in turn may be predefined as having a ranking or priority greater than the “inactive” tuner status. In this example, a particular tuner “Tuner A” having an “active; recording; assignable” tuner status may be specified within the listing ahead of a particular tuner “Tuner B” having an “active; live” tuner status, and ahead of a particular tuner “Tuner C” having an “inactive” tuner status. Here, an ordered set of tuners within the listing may be itemized as “Rank 1: Tuner A; Rank 2: Tuner B; Rank 3: Tuner C.” Other embodiments are possible.
The method 100 may further include allocating (module 108), by the television receiver based on the listing, a particular tuner for recording of the particular broadcast programming at or near the particular date and time. As discussed in further detail below, the television receiver may use or utilize the listing to determine an “optimal” tuner for recording of the particular broadcast programming, and then allocate the optimal tuner for recording of the particular broadcast programming. An optimal tuner may be defined as a tuner having a “higher” or “greater” ranking within the listing than other ones of the plurality tuners.
Such an implementation may be beneficial in many respects. For example, in some DVR-related systems, it may be possible to create a timer using a user-designated tuner to record particular programming. For example, a first user may create a recording timer to initiate recording of a particular program at 9 PM of a particular day using a particular tuner. In this example, however, it may be possible that the particular tuner is in-use at 9 PM of the particular day. For example, a second user may be watching a program using the particular tuner, which in general may be transparent to both the first and second users. Here, assuming that the particular tuner is forcibly allocated by direction of the particular timer, the viewing experience of the second user may be unnecessarily interrupted. The systems and method of the present disclosure may be configured to prevent such an unnecessary interruption by determining a more “optimal” tuner for recording of the programming.
Further scenarios and beneficial aspects associated with selecting a particular tuner of a television receiver in accordance with the present disclosure may be understood in light of the following description in connection with
For example, referring now to
The example system 200 may include a service provider 202, a satellite uplink 204, a plurality of orbiting (e.g., geosynchronous) satellites 206a-c, a satellite dish 208, a PTR (Primary Television Receiver) 210, a plurality of secondary television receivers 212a-b, a plurality of televisions 214a-c, and a plurality of computing devices 216a-b. In the present example, the PTR 210 may at least include a tuner allocation engine 218. The tuner allocation engine 218 may in one aspect be configured for selecting a particular tuner of the PTR 210 for recording particular programming in accordance with the present disclosure, as discussed further below.
The system 200 may also include at least one network 220 that establishes a bi-directional communication path for data transfer between and among the PTR 210, secondary television receivers 212a-b, televisions 214a-c, and computing devices 216a-b of the example system 200. In some embodiments, the network 220 may further establish a bi-directional communication path (not shown) for data transfer between the PTR 210 and the service provider 202. The network 220 is intended to represent any number of terrestrial and/or non-terrestrial network features or elements. For example, the network 220 may incorporate or exhibit any number of features or elements of various wireless and/or hardwired packet-based communication networks such as, for example, a WAN (Wide Area Network) network, a HAN (Home Area Network) network, a LAN (Local Area Network) network, a WLAN (Wireless Local Area Network) network, the Internet, a cellular communications network, and/or any other type of communication network(s) configured such that data may be transferred between and among respective elements of the example system 200.
The PTR 210, and the secondary television receivers 212a-b, as described throughout may generally be any type of television receiver, such as a STB (Set-Top-Box) for example. In another example, the PTR 210, and the secondary television receivers 212a-b, may exhibit functionality integrated as part of or into a television, a DVR, a computer such as a tablet computing device, or any other computing system or device, as well as variations thereof. Further, the PTR 210 and the network 220, together with the secondary television receivers 212a-b, televisions 214a-c, and computing devices 216a-b, may form at least a portion of a particular home computing network, and may each be respectively configured such as to enable communications in accordance with any particular communication protocol(s) and/or standard(s) including, for example, TCP/IP (Transmission Control Protocol/Internet Protocol), DLNA/DTCP-IP (Digital Living Network Alliance/Digital Transmission Copy Protection over Internet Protocol), HDMI/HDCP (High-Definition Multimedia Interface/High-bandwidth Digital Content Protection), etc.
In practice, the satellites 206a-c may be configured to receive uplink signals 222a-b from the satellite uplink 204. In this example, the uplink signals 222a-b may contain one or more transponder streams of particular data or content, such as particular television channel, that is supplied by the service provider 202. For example, each of the respective uplink signals 222a-b may contain various media content such a plurality of encoded HD (High Definition) television channels, various SD (Standard Definition) television channels, on-demand programming, programming information, and/or any other content in the form of at least one transponder stream, and in accordance with an allotted carrier frequency and bandwidth. In this example, different media content may be carried using different ones of the satellites 206a-c. Further, different media content may be carried using different transponders of a particular satellite (e.g., satellite 206a); thus, such media content may be transmitted at different frequencies and/or different frequency ranges. For example, a first and second television channel may be carried on a first carrier frequency over a first transponder of satellite 206a, and a third, fourth, and fifth television channel may be carried on second carrier frequency over a first transponder of satellite 206b, or, the third, fourth, and fifth television channel may be carried on a second carrier frequency over a second transponder of satellite 206a, and etc.
The satellites 206a-c may further be configured to relay the uplink signals 222a-b to the satellite dish 208 as downlink signals 224a-b. Similar to the uplink signals 222a-b, each of the downlink signals 224a-b may contain one or more transponder streams of particular data or content, such as various encoded and/or at least partially electronically scrambled television channels, on-demand programming, etc., in accordance with an allotted carrier frequency and bandwidth. The downlink signals 224a-b, however, may not necessarily contain the same or similar content as a corresponding one of the uplink signals 222a-b. For example, the uplink signal 222a may include a first transponder stream containing at least a first group or grouping of television channels, and the downlink signal 224a may include a second transponder stream containing at least a second, different group or grouping of television channels. In other examples, the first and second group of television channels may have one or more television channels in common. In sum, there may be varying degrees of correlation between the uplink signals 222a-b and the downlink signals 224a-b, both in terms of content and underlying characteristics.
Continuing with the example implementation scenario, the satellite dish 208 may be provided for use to receive television channels (e.g., on a subscription basis) provided by the service provider 202, satellite uplink 204, and/or satellites 206a-c. For example, the satellite dish 208 may be configured to receive particular transponder streams, or downlink signals 224a-b, from one or more of the satellites 206a-c. Based on the characteristics of the PTR 210 and/or satellite dish 208, however, it may only be possible to capture transponder streams from a limited number of transponders concurrently. For example, a tuner of the PTR 210 may only be able to tune to a single transponder stream from a transponder of a single satellite, such as satellite 206a, at a time.
Additionally, the PTR 210, which is communicatively coupled to the satellite dish 208, may subsequently select via tuner (see e.g.,
Further, the PTR 210 may select via tuner, decode, and relay particular transponder streams to one or both of the secondary television receivers 212a-b, which may in turn relay particular transponder streams to a corresponding one of the television 214a and the television 214a for display thereon. For example, the satellite dish 208 and the PTR 210 may, respectively, be configured to receive, decode, and relay at least one television channel to the television 214a by way of the secondary television receiver 212a. Similar to the above-example, the television channel may generally be presented “live,” or from a recording as previously stored on the PTR 210, and may be output to the television 214a by way of the secondary television receiver 212a in accordance with a particular content protection technology and/or networking standard. Other embodiments are possible.
Still further, the satellite dish 208 and the PTR 210 may, respectively, be configured to receive, decode, and relay at least one premium television channel to one or both of the computing devices 216a-b. Similar to the above-examples, the television channel may generally be presented “live,” or from a recording as previously stored on the PTR 210, and may be output to one or both of the computing devices 216a-b in accordance with a particular content protection technology and/or networking standard. Other embodiments are possible.
Referring now to
The EPG 302 may further display or otherwise present a first user-selectable icon 306 (e.g., “Set Timer” icon) that may be selected to set a recording timer to automatically record a particular program for later viewing. In this example, the PTR 210 may exhibit DVR functionality to record programs or programming appearing on various channels as received from satellites 206a-c. For example, and assuming that a current time is sometime prior the time period “9-10 PM,” such as a current time within the time period “8-9 PM” preceding the “9-10 PM” time period, a user may manipulate the cursor 304 to select the “Show S1” as displayed within the EPG 302 for recording by the PTR 210 for later viewing one or more of the televisions 214a-c and the computing devices 216a-b.
For example, during or within the time period “8-9 PM” and following “selection” of the “Show S1,” as shown by stipple shading in
For example, the particular information may include a “Content Name” parameter, a recording “Start” time parameter, a recording “Stop” time parameter, and other parameters as desired. For example, in some embodiments, the information may include a “Tuner” parameter that designates a particular tuner that is to be used to “tune” to the “Show S1,” such that the “Show S1” may be recorded for later viewing. In one embodiment, the “Tuner” parameter may be manually set by a user. For example, and as shown within the timer list 308 of
As may be understood based upon the preceding description, a television viewer, sometimes referred to as a user, may use a stand-alone or integrated DVR, such as the PTR 210, to record individual broadcast television programming for viewing at a later time. A user may further may use the PTR 210 to record multiple instances of broadcast television programming, such as during television “Prime Time,” or “Primetime,” which may for example be between or from 8-10 PM, 7-9 PM, 7-10 PM, etc., on any particular day. The recording of a television channel for such a period of time may be defined by a television service provider, such as the service provider 202 shown in
In some scenarios, rather than a single television channel being recorded at a given time, multiple, such as four, television channels may be recorded over a given time period. For example, during weekday primetime hours, all of the major networks may be simultaneously recorded for the same period of time. Such recording may permit a user to view at a later time any television program that was broadcast during primetime on one of the major networks. When multiple television channels are recorded simultaneously, it may be efficient to use a single tuner to receive all of the multiple television channels being recorded. This may allow other tuners of the television receiver to be used for other operations such as, for example, recording of other television channels and/or presentation of television channels to a user via a viewing device, such as a television.
To implement such functionality, the EPG 302 may further display or otherwise present a second user-selectable icon 310 (e.g., “PTAT” icon) that may be selected to set at least one recording timer to automatically record multiple instances of broadcast television programming, possibly over multiple channels, such as during television “primetime” which may for example be from 8-10 PM, 7-9 PM, 7-10 PM, etc. In this example, a user may manipulate the cursor 304 to select the icon 310 to set a particular “Timer PTAT” to automatically record television “primetime” for later viewing on one or more of the televisions 214a-c and the computing devices 216a-b. In some embodiments, the “Timer PTAT” may be included within the timer list 308 that may, in some embodiments, be presented within the EPG 302 in response to selection of the icon 306 and/or icon 310. Other embodiments are possible.
In general, the “Timer PTAT” when itemized within the timer list 308 may include particular information. Example information associated with the “Timer PTAT” may at least include a “Network(s)” parameter, a “Primetime” parameter, and a “Tuner” parameter. The “Network(s)” parameter may specify at least one network channel to record such as, for example, at least one NBC network channel, at least one ABC network channel, at least one CBS network channel, at least one FOX network channel, and etc. The “Primetime” parameter may specify a particular time period, and frequency, at which television programming appearing on the network channel(s) specified by the “Network(s)” parameter may be recorded, such as from 7 PM to 10 PM on the NBC, ABC, CBS, and FOX networks each weeknight. The “Tuner” parameter may designate a particular tuner that is to be used to “tune” to the television programming appearing on the network channel(s) specified by the “Network(s)” parameter such that the same may be recorded for later viewing. In one embodiment, the “Tuner” parameter may be manually set by a user. In other embodiments, the “Tuner” may be specify a “default” tuner automatically set by the PTR 210 upon creation of the “Timer PTAT.”
As discussed in further detail below, the tuner allocation engine 218 may in one aspect be configured for, in response to an upcoming activation of a scheduled program recording timer that may be listed within the timer list 308, selecting a particular tuner of the PTR 210 in accordance with the present disclosure.
Referring now to
For brevity, the PTR 210 is depicted in a simplified and conceptual form, and may generally include more or fewer elements or components as desired in accordance with the present disclosure. For example, the PTR 210 is shown in
In some embodiments, the PTR 210 and/or the secondary television receivers 212a-b comprise of a STB. In addition to being in the form of an STB, at least the PTR 210 may be incorporated into another device, such as the television 214c. For example, the television 214c may have an integrated television receiver that does not involve an external STB being coupled with the television 214c. A STB may contain some or all of the components of the PTR 210 and/or may be able to perform some or all of the functions of the PTR 210. Accordingly, instances in this document referring to a STB, and steps being performed by a STB, may also be performed, more generally, by the PTR 210 and/or secondary television receivers 212a-b.
Referring still to
The processor 402 may include one or more specialized and/or general-purpose processors configured to perform processes such as tuning to a particular channel, accessing and displaying EPG information from the EPG database 410, and/or receiving and processing input from a user. For example, processor 402 may include one or more processors dedicated to decoding video signals from a particular format, such as MPEG (Moving Picture Experts Group), for output and display on a television and for performing decryption.
The control processor 402b may communicate with the central processor 402a. The control processor 402b may control the recording of television channels based on timers stored in the DVR database 416. The control processor 402b may initiate recording of a television channel by sending a record command along with an indication of the television channel to be recorded to the central processor 402a. The control processor 402b may not send a second record command, when additional recording is to begin at the same time, until an acknowledgement that recording of the first television channel has successfully been received and initiated by the central processor 402a. The control processor 402b may also provide commands to the central processor 402a when recording of a television channel is to cease. In addition to providing commands relating to the recording of television channels, the control processor 402b may provide commands to the central processor 402a that indicate television channels to be output to the decoder 428 for output to a presentation device, such as the television 214c for example.
The control processor 402b may also communicate with the network interface 406 and the user interface 418. The control processor 402b may handle in-coming data from the network interface 406 and the user interface 418. Additionally, the control processor 402b may be configured to output data via the network interface 406.
The tuners 404a-c may be used to tune to television channels, such as television channels transmitted via satellite or cable, such as satellites 206a-c. Each respective one of the tuner 404a-c may be capable of receiving and processing a single stream of data from a satellite transponder, or a cable RF channel, at a given time. As such, a single tuner may tune to a single transponder or, for a cable network, a single cable RF channel. Additionally, one tuner (e.g., tuner 404a) may be used to tune to a television channel on a first transponder stream for display using a television, while another tuner (e.g., tuner 404b) may be used to tune to a television channel on a second transponder for recording and viewing at some other time. Still another tuner (e.g., tuner 404c) may be used to check various television channels to determine if they are available or not. If multiple television channels transmitted on the same transponder stream are desired, a particular tuner (e.g., tuner 404a) may be used to receive the signal containing the multiple television channels for presentation and/or recording. The tuners 404a-c may receive commands from the central processor 402a. Such commands may instruct the tuners 404a-c which frequencies are to be used for tuning.
The network interface 406 may be used to communicate via an alternate communication channel with a television service provider. For example, the primary communication channel may be via satellite, which may be unidirectional to the STB, and the alternate communication channel, which may be bidirectional, may be via a network, such as the Internet. The PTR 210 may be able to communicate with the service provider 202 of
The storage medium 408 may represent a non-transitory computer-readable storage medium. The storage medium 408 may include memory and/or a hard drive. The storage medium 408 may be used to store information received from one or more satellites and/or information received via the network interface 406. The storage medium 408 may store information related to the EPG database 410, the NIT 414, and/or the DVR database 416. Recorded television programs may be stored using the storage medium 408. The storage medium 408 may be partitioned or otherwise divided such that predefined amounts of the storage medium 408 are devoted to storage of omnibus channel files and user-selected television programs.
The EPG database 410 may store information related to television channels and the timing of programs appearing on such television channels. The EPG database 410 may be stored using the storage medium 408, which may be a hard drive. Information from the EPG database 410 may be used to inform users of what television channels or programs are popular and/or provide recommendations to the user. Information from the EPG database 410 may provide the user with a visual interface (e.g., EPG 302) displayed by a television that allows a user to browse and select television channels and/or television programs for viewing and/or recording. Information used to populate the EPG database 410 may be received via the network interface 406 and/or via satellites, such as satellites 206a-c of
In addition to being used to provide users with information about scheduled programming, information from the EPG database 410 may be used to determine when television programs begin and end for the purposes of recording. For instance, when a channel-specific file is recorded that contains multiple television channels, the start and end of time of specific television programs within the channel-specific file may be based on the start and end times indicated in the EPG database 410. Other data may be stored within the EPG database 410 that may be useful in managing channel-specific files, such as series identifiers and episode identifiers, which may be used by a television service provider to identify particular television programs.
The decoder 428 may serve to convert encoded video and audio into a format suitable for output to a display device. For instance, the decoder 428 may receive MPEG video and audio from the storage medium 408, or the descrambling engine 424, to be output to a television. MPEG video and audio from the storage medium 224 may have been recorded to the DVR database 416 as part of a previously-recorded television program. The decoder 428 may convert the MPEG video and audio into a format appropriate to be displayed by a television or other form of display device and audio into a format appropriate to be output from speakers, respectively.
The television interface 412 may serve to output a signal to a television, or another form of display device, in a proper format for display of video and playback of audio. As such, the television interface 412 may output one or more television channels, stored television programming from the storage medium 408, such as television programs from the DVR database 416 and/or information from the EPG database 410 for example, to a television for presentation.
The NIT 414 may store information used by the PTR 210 to access various television channels. The NIT 414 may be stored using the storage medium 408. Information used to populate the NIT 414 may be received via satellite, or cable, via the tuners 404a-c and/or may be received via the network interface 406 from a service provider. As such, information present in the NIT 414 may be periodically updated. The NIT 414 may be locally-stored by the PTR 210 using the storage medium 408. Information that may be present in the NIT 414 may include, for example: television channel numbers, a satellite identifier, a frequency identifier, a transponder identifier, an ECM (Entitlement Control Message) PID (Packet Identifier), one or more audio PIDs, and a video PID. A second audio PID of a channel may correspond to a SAP (Second Audio Program) program, such as in another language. In some embodiments, the NIT 414 may be divided into additional tables. For example, rather than the specific audio PIDs and video PIDs being present in the NIT 414, a channel identifier may be present within NIT 414 which may be used to look up the audio PIDs and video PIDs in another table, such as the PMT 426. For example, the PMT 426 may store information on audio PIDs and video PIDs for television channels that are transmitted on a transponder frequency.
Table 1 provides a simplified example of the NIT 414 for several television channels. It should be understood that in other embodiments, many more television channels may be represented in the NIT 414. The NIT 414 may be at least periodically updated by a television service provider. As such, television channels may be reassigned to different satellites and/or transponders, and the PTR 210 may be able to handle this reassignment as long as the NIT 414 is updated.
Based on information in the NIT 414, it may be possible to determine the proper satellite and transponder to which to tune for a particular television channel. In some embodiments, the NIT 414 may list a particular frequency to which to tune for a particular television channel. Once tuned to the proper satellite/transponder/frequency, the PMT PID may be used to retrieve a program management table that indicates the PIDs for audio and video streams of television channels transmitted by that transponder.
It should be understood that the values provided in Table 1 are for example purposes only. Actual values, including how satellites and transponders are identified, may vary. Additional information may also be stored in NIT 414. Additional information on how the NIT 414, as indicated in Table 1, may be used is provided in reference to
A DVR may permit a television channel to be recorded for a period of time. DVR functionality of the PTR 210 may be managed by the control processor 402b. The control processor 402b may coordinate the television channel, start time, and stop time of when recording of a television channel is to occur. The DVR database 416 may store information related to the recording of television stations. The DVR database 416 may store timers that are used by the control processor 402b to determine when a television channel should be tuned to and its programs recorded to the DVR database 416. However, other embodiments are possible. For example, in some embodiments, the storage medium 408 may store timers. Timer files may be defined as a daily_schedule_db.dat file and a gloal_timer_db.dat file. In general, when a “new” timer is created, a “new” entry may be added into the daily_schedule_db.dat and gloal_timer_db.dat files, which may include all timer related information such as channel number, start time, duration, etc. Further, a limited amount of the storage medium 408 may be devoted to the DVR database 416. Timers may be set by a service provider and/or one or more users of the PTR 210.
DVR functionality of the control processor 402b may have multiple modes. For example, DVR functionality of the control processor 402b may be configured to record individual television programs selected by a user to the DVR database 416. Using the EPG database 410, a user may select a particular television program. Based on the date, time period, and television channel indicated by the EPG database 410, the control processor 402b may record the associated television program to the DVR database 416. In another example, the DVR database 416 may be used to store recordings of predefined periods of time on one or more television channels. These predefined periods of time may include one or more television programs. For example, primetime on a particular television network may be recorded each weekday night. Further, multiple television channels may be recorded for such predefined periods of time. Such recording of television channels for predefined periods of time may be defined by a television service provider (e.g., service provider 202).
As an example of this second mode of DVR functionality, a television service provider may configure the PTR 210 to record television programming on multiple, predefined television channels for a predefined period of time, on predefined dates. For instance, a television service provider may configure the PTR 210 such that television programming may be recorded from 7 PM to 10 PM on the NBC, ABC, CBS, and FOX networks each weeknight. When a television program is selected for recording by a user and is also specified for recording by the television service provider, the user selection may serve as an indication to save the television program for an extended time, beyond the time which the predefined recording would otherwise be saved.
The user interface 418 may include a remote control, physically separate from PTR 210, and/or one or more buttons on the PTR 210 that allows a user to interact with the PTR 210. The user interface 418 may be used to select a television channel for viewing, view information from the EPG database 410, and/or program a timer stored to the DVR database 416 wherein the timer may be used to control the DVR functionality of the control processor 402b.
Referring back to tuners 404a-c, television channels received via satellite, or cable, may contain at least some scrambled data. Packets of audio and video may be scrambled to prevent unauthorized users, such as nonsubscribers, from receiving television programming without paying the television service provider. When one of the tuners 404a-c is receiving data from a particular transponder of a satellite, the transponder stream may be a series of data packets corresponding to multiple television channels. Each data packet may contain a PID, which, in combination with the NIT 414 and/or the PMT 426, can be determined to be associated with particular television channel. Particular data packets, referred to as ECMs may be periodically transmitted. ECMs may be associated with another PID and may be encrypted; the PTR 210 may use the smart card 422 to decrypt ECMs. Decryption of an ECM may only be possible when the user (e.g., PTR 210) has authorization to access the particular television channel associated with the ECM. When an ECM is determined to correspond to a television channel being stored and/or displayed, the ECM may be provided to the smart card 422 for decryption.
When the smart card 422 receives an encrypted ECM, the smart card 422 may decrypt the ECM to obtain some number of control words. In some embodiments, from each ECM received by the smart card 422, two control words are obtained. In some embodiments, when the smart card 422 receives an ECM, it compares the ECM to the previously received ECM. When the two ECMs match, the second ECM is not decrypted because the same control words would be obtained. In other embodiments, each ECM received by the smart card 422 is decrypted; however, when a second ECM matches a first ECM, the outputted control words will match; thus, effectively, the second ECM does not affect the control words output by the smart card 422. The smart card 422 may be permanently part of the PTR 210 or may be configured to be inserted and removed from PTR 210.
The central processor 402a may be in communication with the tuners 404a-c and the control processor 402b. The central processor 402a may be configured to receive commands from the control processor 402b. Such commands may indicate when to start/stop recording a television channel and/or when to start/stop causing a television channel to be output to a television. The central processor 402a may control the tuners 404a-c. The central processor 402a may provide commands to the tuners 404a-c that instruct the tuners which satellite, transponder, and/or frequency to tune to. From the tuners 404a-c, the central processor 402a may receive transponder streams of packetized data. As previously detailed, some or all of these packets may include a PID that identifies the content of the packet.
The central processor 402a may be configured to create at least one PID filter 420 that sorts packets received from the tuners 404a-c based on the PIDs. When a tuner is initially tuned to a particular frequency, such as a particular transponder of a satellite, a PID filter may be created based on a PID of PMT data. The PID of PMT data packets may be known because it is stored as part of the NIT 414. From the PMT data packets, the PMT 426 may be constructed by central processor 402a. Table 2 provides an exemplary extract of a PMT. The PMT 426 may be specific to a particular transponder. As such, when tuning to a different transponder occurs, a new PMT may be created for the different transponder.
Accordingly, based on the information present in the PMT 426, the audio and video PIDs for specific television channels may be identified. A television channel may have multiple audio PIDs due to a second audio program, which may be in a different language.
It should be understood that the values provided in Table 2 are for example purposes only. Actual values may vary. Additional information or less information may also be stored in the PMT 426.
The PID filter 420 may be configured to filter data packets based on PIDs. In some embodiments, the PID filter 420 is created and executed by central processor 402a. In other embodiments, separate hardware may be used to create and execute multiple PID filters. Depending on a television channel selected for recording/viewing, a PID filter may be created to filter the video and audio packets associated with the television channel, based on the PID assignments present in the PMT 426. For example, when a transponder data stream includes multiple television channels, data packets corresponding to a television channel that is not desired to be stored or displayed by the user, may be ignored by PID filters. As such, only data packets corresponding to the one or more television channels desired to be stored and/or displayed may be filtered and passed to either the descrambling engine 424 or the smart card 422; other data packets may be ignored. For each television channel, a stream of video packets, a stream of audio packets, one or both of the audio programs, and/or a stream of ECM packets may be present, each stream identified by a PID. In some embodiments, a common ECM stream may be used for multiple television channels. Additional data packets corresponding to other information, such as updates to the NIT 414, may be appropriately routed by the PID filter 420. At a given time, one or multiple PID filters may be executed by the central processor 402a.
The descrambling engine 424 may use the control words output by the smart card 422 in order to descramble video and/or audio corresponding to television channels for storage and/or presentation Video and/or audio data contained in the transponder data stream received by the tuners 404a-c may be scrambled. Video and/or audio data may be descrambled by descrambling engine 424 using a particular control word. Which control word output by the smart card 422 to be used for successful descrambling may be indicated by a scramble control identifier present within the data packet containing the scrambled video or audio. Descrambled video and/or audio may be output by the descrambling engine 424 to the storage medium 408 for storage in the DVR database 416 and/or to the decoder 428 for output to a television or other presentation equipment via the television interface 412.
For simplicity, the PTR 210 of
Referring now to
In practice, the timer activation module 502 may be configured to receive, from the DVR database 416 for example, an indication of an upcoming or imminent activation of a scheduled program recording timer that is stored to the DVR database 416. As mentioned above, the DVR database 416 may store timers that are used by the control processor 402b to determine when a television channel should be tuned to and its programs recorded to the DVR database 416. Timing of the indication may be a user-configurable parameter. For example, the DVR database 416 and/or the control processor 402b may be configured to generate and transfer the indication to the timer activation module 502 at time of 10 seconds, or 20 seconds, or 30 seconds, or 45 seconds, etc., prior to activation of the scheduled program recording timer. Other embodiments are possible.
The timer activation module 502 may activate the timer status module 504 upon receiving the indication of upcoming activation of the scheduled program recording timer. In response, the timer status module 504 may query the control processor 402b to determine a current status of each of the tuners 404a-c, and generate a listing that ranks each of the tuners 404a-c against each other based on each respective current status. Each of the tuners 404a-c may generally be in one of an inactive state and an active state. When, for example, the tuner 404a is not currently in-use, the control processor 402b may indicate to the timer status module 504 a status of the tuner 404a of “inactive.” When, for example, the tuner 404b is currently in-use, the control processor 402b may indicate to the timer status module 504 a status of the tuner 404b of “active.” When a particular one of the tuners 404a-c is currently in an active state, the control processor 402b may further indicate to the timer status module 504 a “type” of status of the particular one of the tuners 404a-c, and whether or not information is available as to the anticipated status of the particular one of the tuners 404a-c at a “start” time associated with the scheduled program recording timer.
For example, the control processor 402b may indicate to the timer status module 504 that the tuner 404c is currently being used for the recording of particular programming, but will not be recording at a time of activation of the scheduled program recording timer. In this example, the tuner 404c is known to be currently recording, but will be available for the recording of particular broadcast programming associated with the scheduled program recording timer. The tuner 404c in this scenario may be considered an “optimal” tuner for recording of the particular broadcast programming, and may be assigned a “highest” or “greatest” ranking to quantify the tuner 404c as an “optimal” tuner. In one example, a current status of an active tuner in this scenario may be defined as “active; recording; assignable.” Other embodiments are possible.
In another example, the control processor 402b may indicate to the timer status module 504 that the tuner 404c is currently being used for the recording of particular programming, but will not be recording at a time of activation of the scheduled program recording timer, and further that the tuner 404c is currently being used for a PIP (Picture in Picture) session. In this example, the tuner 404c is known to be currently recording, but will be available for recording of particular broadcast programming associated with the scheduled program recording timer, and further is being used for a PIP session. The tuner 404c in this scenario may not be considered an optimal tuner for recording of the particular broadcast programming, and may be assigned a ranking less than the highest or greatest ranking that would otherwise quantify the tuner 404c as an optimal tuner. In one example, a current status of an active tuner in this scenario may be defined as “active; recording; assignable; PIP.” Other embodiments are possible.
In another example, the control processor 402b may indicate to the timer status module 504 that the tuner 404c is currently being used for the recording of particular programming, but will not be recording at a time of activation of the scheduled program recording timer, and further that the tuner 404c is currently being used to select the particular programming for presentation by a display device. In this example, the tuner 404c is known to be currently recording, but will be available for recording of particular broadcast programming associated with the scheduled program recording timer, and further is being used for “live” viewing of the particular programming that is being recorded. The tuner 404c in this scenario may not be considered an optimal tuner for recording of the particular broadcast programming, and may be assigned a ranking less than the highest or greatest ranking that would otherwise quantify the tuner 404c as an optimal tuner. In one example, a current status of an active tuner in this scenario may be defined as “active; recording; assignable; live.” Other embodiments are possible.
In another example, the control processor 402b may indicate to the timer status module 504 that the tuner 404c is currently being used for “live” viewing of particular programming, and further is being used for a PIP session. The tuner 404c in this scenario may not be considered an optimal tuner for recording of the particular broadcast programming associated with the scheduled program recording timer, and may be assigned a ranking less than the highest or greatest ranking that would otherwise quantify the tuner 404c as an optimal tuner. In one example, a current status of an active tuner in this scenario may be defined as “active; live; PIP.” Other embodiments are possible.
In another example, the control processor 402b may indicate to the timer status module 504 that the tuner 404c is currently being used for “live” viewing of particular programming. The tuner 404c in this scenario may not be considered an optimal tuner for recording of the particular broadcast programming associated with the scheduled program recording timer, and may be assigned a ranking less than the highest or greatest ranking that would otherwise quantify the tuner 404c as an optimal tuner. In one example, a current status of an active tuner in this scenario may be defined as “active; live.” Other embodiments are possible.
In another example, the control processor 402b may indicate to the timer status module 504 that the tuner 404c is currently being used for “live” viewing of particular programming, and further is “delayed” some manner. In this example, the tuner 404c is currently being used for “live” viewing of particular programming, but a “trick” mode may be engaged by a user such as by activation of a “pause” function or “skip back” function so that the particular programming is time delayed. The tuner 404c in this scenario may not be considered an optimal tuner for recording of the particular broadcast programming associated with the scheduled program recording timer, and may be assigned a ranking less than the highest or greatest ranking that would otherwise quantify the tuner 404c as an optimal tuner. In one example, a current status of an active tuner in this scenario may be defined as “active; live; delayed.” Other embodiments are possible.
As described in further detail below in connection with
Rank 1: active; recording; assignable.
Rank 2: active; recording; assignable; PIP.
Rank 3: active; recording; assignable; live.
Rank 4: inactive.
Rank 5: active; live; PIP.
Rank 6: active; live.
Rank 7: active; live; delayed.
Here, the tuner status “active; recording; assignable” is of greater rank or priority than the tuner status “active; recording; assignable; PIP,” which is of greater rank or priority than the tuner status “active; recording; assignable; live,” which is of greater rank or priority than the tuner status “inactive,” which is of greater rank or priority than the tuner status “active; live; PIP,” which is of greater rank or priority than the tuner status “active; live,” and which is of greater rank or priority than the tuner status “active; live; delayed.” Other embodiments are possible.
As mentioned above, the timer status module 504 may further generate a listing that ranks each of the tuners 404a-c against each other based on each respective current status in response to receiving the indication of upcoming activation of the scheduled program recording timer. Continuing with the above-example tuner ranking or priority hierarchical structure, and assuming a particular determined status of each of the tuners 404a-c for purpose of example, the tuner 404a when associated with the “active; recording; assignable” tuner status may be specified within the listing ahead of the tuner 404b, when the tuner 404b is associated with the “active; recording; assignable; live” tuner status, and ahead of the tuner 404c, when the tuner 404c is associated with the “inactive” tuner status. Here, the ordered set of tuners within the listing may be itemized as “Rank 1: tuner 404a; Rank 2: tuner 404b; Rank 3: tuner 404c.” Other embodiments are possible.
The timer status module 504 may activate the tuner allocation module 506 upon generating the listing that ranks each of the tuners 404a-c against each other based on each respective current status. In response, the tuner allocation module 506 may allocate a particular one of the tuners 404a-c for recording of the particular broadcast programming associated with the scheduled program recording timer. Continuing with the above-example ordered set of tuners, the tuner allocation module 506 may utilize the listing “Rank 1: tuner 404a; Rank 2: tuner 404b; Rank 3: tuner 404c,” determine that tuner 404a is the “optimal” tuner for recording of the particular broadcast programming, and allocate the tuner 404a for recording of the particular broadcast programming. The tuner 404a is “optimal” because this tuner has a “higher” or “greater” ranking or priority within the listing than the tuner 404b and the tuner 404c.
There may be a number of benefits and advantages associated with such an implementation. For example, the tuner 404a is selected at least instead of tuner 404c, which in the example scenario is associated with the “inactive” tuner status. Since the tuner 404c is not allocated for recording of the particular broadcast programming, this tuner may remain “available” for other purposes. For example, the tuner 404c may be considered “at the ready” such that when a user turns on the television 214c there will be no conflict with providing the user instant access to either live or recoded programming. Other benefits and advantages are possible as well.
Referring now to
At 602, the television receiver may set a counter to N=1.
At 604, the television receiver may determine a current status of a particular tuner N of a plurality of tuners M of the television receiver. In this example, N and M are integer values where N is less than or equal M. Initially, this may correspond to television receiver determining a current status of a first tuner (e.g., “Tuner 1”) of the plurality of tuners M of the television receiver. As mentioned above in connection with
At 606, the television receiver may assign a ranking to the particular tuner N based on the current status of a particular tuner N. Continuing with the above example, the television receiver may: a) assign a “Rank 1” to the particular tuner N when the current status is determined “active; recording; assignable”; b) assign a “Rank 2” to the particular tuner N when the current status is determined “active; recording; assignable; PIP”; c) assign a “Rank 3” to the particular tuner N when the current status is determined “active; recording; assignable; live”; d) assign a “Rank 4” to the particular tuner N when the current status is determined “inactive”; e) assign a “Rank 5” to the particular tuner N when the current status is determined “active; live; PIP”; f) assign a “Rank 6” to the particular tuner N when the current status is determined “active; live”; g) assign a “Rank 7” to the particular tuner N when the current status of the particular tuner N is determined “active; live; delayed.”
At 608, the television receiver may populate a listing based on the ranking of the particular tuner N. Initially, the listing may only have a single entry, such as “Rank 3; Tuner 1” for example. When N is greater than 1 but less than M however, the listing may have multiple entries such as “Rank 6; Tuner 1” and “Rank 6; Tuner 2” and “Rank 3; Tuner 3.” Other embodiments are possible.
At 610, the television receiver may determine whether other tuners of the television receiver have yet to be ranked. When the television receiver determines that no other tuners of the television receiver have yet to be ranked, process flow may branch to 612. At 612, the television receiver may select a particular tuner of the plurality of tuners M having a “higher” or “greater” ranking within the listing than other ones of the plurality tuners M, and then allocate the particular tuner for recording of particular broadcast programming associated with a particular timer.
When the television receiver determines that other tuners of the television receiver have yet to be ranked, process flow may branch to 614 that iterates the counter to N=N+1. In this example, process flow proceeds in a loop until at 610 the television receiver determines that no other tuners of the television receiver have yet to be ranked. At 612, the television receiver may then select a particular tuner of the plurality of tuners M for recording of particular broadcast programming associated with a particular timer in manner as discussed above.
There may be a number of different scenarios that may arise when allocating a particular tuner for recording of the particular broadcast programming according to the principles of the present disclosure.
For example, in some DVR-related systems, it may be possible for a user to set-up a plurality of timers to activate or “fire” at a substantially similar or same time, a number of the timers being the same as the number of tuners available to the system. In this example, activation of the timers may not be performed in parallel. Rather, activation of timers may be performed in sequence or series. For example, even though being set to activate at a substantially similar or same time, a “Timer A” may fire before a “Timer B,” which may fire before a “Timer C.” Here, process flow in ranking of the tuners based on a predefined tuner ranking or priority, such as referred to above in connection with at least
For example, in practice, a first iteration of the example method 600 of
In other examples, in some DVR-related systems, it may be possible that all available tuners of the system are being used to watch “live” programming. In this example, a “Timer A” may fire during a time when all available tuners of the system are being used to watch “live” programming. This may correspond to all tuners associated with a “Rank 6” status or priority, such as referred to above in connection with at least
For example, and referring now additionally to
The computer device 700 is shown comprising hardware elements that may be electrically coupled via a bus 702 (or may otherwise be in communication, as appropriate). The hardware elements may include a processing unit with one or more processors 704, including without limitation one or more general-purpose processors and/or one or more special-purpose processors (such as digital signal processing chips, graphics acceleration processors, and/or the like); one or more input devices 706, which can include without limitation a remote control, a mouse, a keyboard, and/or the like; and one or more output devices 708, which can include without limitation a presentation device (e.g., television), a printer, and/or the like.
The computer system 700 may further include (and/or be in communication with) one or more non-transitory storage devices 710, which can comprise, without limitation, local and/or network accessible storage, and/or can include, without limitation, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random access memory, and/or a read-only memory, which can be programmable, flash-updateable, and/or the like. Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like.
The computer device 700 might also include a communications subsystem 712, which can include without limitation a modem, a network card (wireless or wired), an infrared communication device, a wireless communication device, and/or a chipset (such as a Bluetooth™ device, an 802.11 device, a WiFi device, a WiMax device, cellular communication facilities (e.g., GSM, WCDMA, LTE, etc.), and/or the like. The communications subsystem 712 may permit data to be exchanged with a network (such as the network described below, to name one example), other computer systems, and/or any other devices described herein. In many embodiments, the computer system 700 will further comprise a working memory 714, which may include a random access memory and/or a read-only memory device, as described above.
The computer device 700 also can comprise software elements, shown as being currently located within the working memory 714, including an operating system 716, device drivers, executable libraries, and/or other code, such as one or more application programs 718, which may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein. By way of example, one or more procedures described with respect to the method(s) discussed above, and/or system components might be implemented as code and/or instructions executable by a computer (and/or a processor within a computer); in an aspect, then, such code and/or instructions can be used to configure and/or adapt a general purpose computer (or other device) to perform one or more operations in accordance with the described methods.
A set of these instructions and/or code might be stored on a non-transitory computer-readable storage medium, such as the storage device(s) 710 described above. In some cases, the storage medium might be incorporated within a computer system, such as computer system 700. In other embodiments, the storage medium might be separate from a computer system (e.g., a removable medium, such as flash memory), and/or provided in an installation package, such that the storage medium can be used to program, configure, and/or adapt a general purpose computer with the instructions/code stored thereon. These instructions might take the form of executable code, which is executable by the computer device 700 and/or might take the form of source and/or installable code, which, upon compilation and/or installation on the computer system 700 (e.g., using any of a variety of generally available compilers, installation programs, compression/decompression utilities, etc.), then takes the form of executable code.
It will be apparent to those skilled in the art that substantial variations may be made in accordance with specific requirements. For example, customized hardware might also be used, and/or particular elements might be implemented in hardware, software (including portable software, such as applets, etc.), or both. Further, connection to other computing devices such as network input/output devices may be employed.
As mentioned above, in one aspect, some embodiments may employ a computer system (such as the computer device 700) to perform methods in accordance with various embodiments of the invention. According to a set of embodiments, some or all of the procedures of such methods are performed by the computer system 700 in response to processor 704 executing one or more sequences of one or more instructions (which might be incorporated into the operating system 716 and/or other code, such as an application program 718) contained in the working memory 714. Such instructions may be read into the working memory 714 from another computer-readable medium, such as one or more of the storage device(s) 710. Merely by way of example, execution of the sequences of instructions contained in the working memory 714 may cause the processor(s) 704 to perform one or more procedures of the methods described herein.
The terms “machine-readable medium” and “computer-readable medium,” as used herein, may refer to any medium that participates in providing data that causes a machine to operate in a specific fashion. In an embodiment implemented using the computer device 700, various computer-readable media might be involved in providing instructions/code to processor(s) 704 for execution and/or might be used to store and/or carry such instructions/code. In many implementations, a computer-readable medium is a physical and/or tangible storage medium. Such a medium may take the form of a non-volatile media or volatile media. Non-volatile media may include, for example, optical and/or magnetic disks, such as the storage device(s) 710. Volatile media may include, without limitation, dynamic memory, such as the working memory 714.
Example forms of physical and/or tangible computer-readable media may include a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, a RAM, a PROM, EPROM, a FLASH-EPROM, any other memory chip or cartridge, or any other medium from which a computer can read instructions and/or code.
Various forms of computer-readable media may be involved in carrying one or more sequences of one or more instructions to the processor(s) 704 for execution. By way of example, the instructions may initially be carried on a magnetic disk and/or optical disc of a remote computer. A remote computer might load the instructions into its dynamic memory and send the instructions as signals over a transmission medium to be received and/or executed by the computer system 700.
The communications subsystem 712 (and/or components thereof) generally will receive signals, and the bus 702 then might carry the signals (and/or the data, instructions, etc. carried by the signals) to the working memory 714, from which the processor(s) 704 retrieves and executes the instructions. The instructions received by the working memory 714 may optionally be stored on a non-transitory storage device 710 either before or after execution by the processor(s) 704.
The methods, systems, and devices discussed above are examples. Various configurations may omit, substitute, or add various method steps or procedures, or system components as appropriate. For instance, in alternative configurations, the methods may be performed in an order different from that described, and/or various stages may be added, omitted, and/or combined. Also, features described with respect to certain configurations may be combined in various other configurations. Different aspects and elements of the configurations may be combined in a similar manner. Also, technology evolves and, thus, many of the elements are examples and do not limit the scope of the disclosure or claims.
Specific details are given in the description to provide a thorough understanding of example configurations (including implementations). However, configurations may be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques have been shown without unnecessary detail in order to avoid obscuring the configurations. This description provides example configurations only, and does not limit the scope, applicability, or configurations of the claims. Rather, the preceding description of the configurations will provide those skilled in the art with an enabling description for implementing described techniques. Various changes may be made in the function and arrangement of elements without departing from the spirit or scope of the disclosure.
Also, configurations may be described as a process which is depicted as a flow diagram or block diagram. Although each may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be rearranged. A process may have additional steps not included in the figure. Furthermore, examples of the methods may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware, or microcode, the program code or code segments to perform the necessary tasks may be stored in a non-transitory computer-readable medium such as a storage medium. Processors may perform the described tasks.
Furthermore, the example embodiments described herein may be implemented as logical operations in a computing device in a networked computing system environment. The logical operations may be implemented as: (i) a sequence of computer implemented instructions, steps, or program modules running on a computing device; and (ii) interconnected logic or hardware modules running within a computing device.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
This application claims the benefit of U.S. Provisional Patent Application No. 61/611,483, filed 15 Mar. 2012, entitled “RECEPTION, RECORDING, STORAGE, AND MANIPULATION OF MULTIPLE TELEVISION CHANNELS,” the entirety of which is hereby incorporated by reference for all intents and purposes.
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 |
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 |
6453115 | Boyle | Sep 2002 | B1 |
6628891 | Vantalon et al. | Sep 2003 | B1 |
6701528 | Arsenault et al. | Mar 2004 | B1 |
6766523 | Herley | Jul 2004 | B2 |
6798971 | Potrebic | Sep 2004 | B2 |
6938208 | Reichardt | Aug 2005 | B2 |
7024676 | Klopfenstein | Apr 2006 | B1 |
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 |
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 |
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 |
20010028782 | Ohno et al. | Oct 2001 | A1 |
20010033736 | Yap et al. | Oct 2001 | A1 |
20010034787 | Takao et al. | Oct 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 et al. | 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 | Agnihotri 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 |
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 |
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 |
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 et al. | Jan 2005 | A1 |
20050034171 | Benya | Feb 2005 | A1 |
20050083865 | Ashley et al. | Apr 2005 | A1 |
20050120049 | Kanegae et al. | Jun 2005 | A1 |
20050125683 | Matsuyama 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 |
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 |
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 |
20070039032 | Goldey et al. | Feb 2007 | A1 |
20070061378 | Lee et al. | Mar 2007 | A1 |
20070154163 | Cordray | 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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
20120198501 | Ruan et al. | Aug 2012 | A1 |
20120236933 | Saitoh | Sep 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 |
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 |
20130216208 | Kummer et al. | Aug 2013 | A1 |
20130223814 | Casagrande | Aug 2013 | A1 |
20130243397 | Minnick 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 |
20140126889 | Kummer et al. | May 2014 | A1 |
20140130094 | Kirby et al. | May 2014 | A1 |
20140147102 | Shartzer | 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 | Potrebic | 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 |
Number | Date | Country |
---|---|---|
1595975 | Mar 2005 | CN |
1615017 | May 2005 | CN |
101202600 | Jun 2008 | CN |
101310532 | Nov 2008 | CN |
101 404 780 | Apr 2009 | CN |
101978690 | Feb 2011 | CN |
0 903 743 | Mar 1999 | EP |
0 973 333 | Jan 2000 | EP |
1 001 631 | May 2000 | EP |
1168 347 | Jan 2002 | EP |
1372339 | Dec 2003 | EP |
1 447 983 | Aug 2004 | 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 |
1 667 452 | Nov 2011 | EP |
2 403 239 | Jan 2012 | EP |
2 541 929 | Jan 2013 | 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 |
9493CHEN2013 | 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 | Jul 2004 | WO |
2007047410 | Apr 2007 | WO |
2008010118 | Jan 2008 | WO |
2008010689 | Jan 2008 | WO |
2008060486 | May 2008 | WO |
2011027236 | Mar 2011 | WO |
2011081729 | Jul 2011 | WO |
2012003693 | Jan 2012 | WO |
2013028824 | Feb 2013 | WO |
2013028835 | Feb 2013 | WO |
2013028829 | 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 |
2016066443 | May 2016 | WO |
2016111817 | Jul 2016 | WO |
Entry |
---|
U.S. Appl. No. 13/795,914, filed Mar. 6, 2013, Non-Final Office Action mailed Oct. 11, 2013, 17 pages. |
U.S. Appl. No. 13/856,752, filed Apr. 4, 2013 Notice of Allowance mailed Feb. 10, 2015, 20 pages. |
U.S. Appl. No. 13/797,173, filed Mar. 12, 2013 Notice of Allowance mailed Feb. 26, 2015, 19 pages. |
U.S. Appl. No. 13/793,636, filed Mar. 11, 2013, Notice of Allowance mailed Jan. 28, 2015, 43 pages. |
U.S. Appl. No. 13/800,477, filed Mar. 13, 2013 Notice of Allowance mailed Feb. 18, 2015, 18 pages. |
Extended European Search Report for EP 12825474 mailed Jan. 7, 2015, 6 pages. |
Extended European Search Report for EP 12825430 mailed Feb. 3, 2015, all 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. |
International Search Report and Written Opinion of PCT/US2012/51992 mailed Nov. 2, 2012, 15 pages. |
International Search Report and Written Opinion of PCT/US2012/51987 mailed Oct. 23, 2012, 20 pages. |
International Search Report and Written Opinion of PCT/US2012/051984 mailed Nov. 5, 2012, 13 pages. |
International Search Report and Written Opinion of PCT/US2012/52002 mailed Oct. 16, 2012, 17 pages. |
International Preliminary Report on Patentability for PCT/US2012/052002 mailed on Apr. 17, 2014, 10 pages. |
International Search Report and Written Opinion of PCT/US2012/51964 mailed Nov. 2, 2012, 13 pages. |
International Search Report and Written Opinion of PCT/US2012/052011 mailed Dec. 17, 2012, 44 pages. |
International Preliminary Report on Patentability, PCT/US2012/052011, mailed on Mar. 6, 2014, 6 pages. |
International Preliminary Report on Patentability, PCT/US2012/051984, mailed on Mar. 6, 2014, 8 pages. |
International Preliminary Report on Patentability, PCT/US2012/051964, mailed on Apr. 10, 2014, 7 pages. |
International Preliminary Report on Patentability, PCT/US2012/051992, mailed on Apr. 3, 2014, 7 pages. |
International Preliminary Report on Patentability, PCT/US2012/051987, mailed on Mar. 6, 2014, 7 pages. |
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. |
U.S. Appl. No. 13/149,852, filed May 31, 2011, Non-Final Office Action mailed Dec. 12, 2012, 9 pages. |
U.S. Appl. No. 13/149,852, filed May 31, 2011, Final Office Action mailed Mar. 26, 2013, 13 pages. |
U.S. Appl. No. 13/149,852, filed May 31, 2011, Notice of Allowance mailed Jul. 11, 2013, 13 pages. |
U.S. Appl. No. 13/286,157, filed Oct. 31, 2011, Non-Final Office Action mailed Jan. 17, 2013, 20 pages. |
U.S. Appl. No. 13/286,157, filed Oct. 31, 2011, Non-Final Office Action mailed Jul. 25, 2013, 49 pages. |
U.S. Appl. No. 13/286,157, filed Oct. 31, 2011, Notice of Allowance mailed Feb. 3, 2014, 81 pages. |
U.S. Appl. No. 13/215,702, filed Aug. 23, 2011, Notice of Allowance mailed Feb. 11, 2013, 13 pages. |
U.S. Appl. No. 13/288,002, filed Nov. 2, 2011, Non-Final Office Action mailed Sep. 26, 2013, 15 pages. |
U.S. Appl. No. 13/288,002, filed Nov. 2, 2011, Final Office Action mailed Mar. 27, 2014, 20 pages. |
U.S. Appl. No. 13/302,852, filed Nov. 22, 2011, Non-Final Rejection mailed May 23, 2013, 19 pages. |
U.S. Appl. No. 13/302,852, filed Nov. 22, 2011, Final Rejection mailed Dec. 9, 2015, 23 pages. |
U.S. Appl. No. 13/324,831, filed Dec. 13, 2011, Non-Final Office Action mailed Feb. 28, 2013, 23 pages. |
U.S. Appl. No. 13/324,831, filed Dec. 13, 2011, Notice of Allowance mailed Sep. 4, 2013, 22 pages. |
U.S. Appl. No. 13/292,047, filed Nov. 8, 2011, Non-Final Office Action mailed Jan. 18, 2013, 17 pages. |
U.S. Appl. No. 13/292,047, filed Nov. 8, 2011, Final Office Action mailed Aug. 19, 2013, 17 pages. |
U.S. Appl. No. 13/614,899, filed Sep. 13, 2012, Non-Final Office Action mailed Feb. 5, 2013, 17 pages. |
U.S. Appl. No. 13/614,899, filed Sep. 13, 2012, Non-Final Office Action mailed Sep. 17, 2013, 17 pages. |
U.S. Appl. No. 13/614,899, filed Sep. 13, 2012, Final Office Action mailed Mar. 17, 2013, 41 pages. |
U.S. Appl. No. 13/291,014, filed Nov. 7, 2012, Non-Final Office Action mailed Mar. 29, 2013, 21 pages. |
U.S. Appl. No. 13/291,014, filed Nov. 7, 2011, Notice of Allowance mailed Aug. 7, 2013, 16 pages. |
U.S. Appl. No. 13/215,598, filed Aug. 23, 2012, Non-Final Office Action mailed Jun. 20, 2013, 15 pages. |
U.S. Appl. No. 13/215,598, filed Aug. 23, 2011, Final Office Action mailed Nov. 21, 2013, 23 pages. |
U.S. Appl. No. 13/215,598, filed Aug. 23, 2011, Non-Final Office Action mailed Feb. 6, 2014, 12 pages. |
U.S. Appl. No. 13/215,655, filed Aug. 23, 2011, Non-Final Office Action mailed Sep. 6, 2013, 27 pages. |
U.S. Appl. No. 13/215,655, filed Aug. 23, 2011, Final Office Action mailed Dec. 18, 2013, 20 pages. |
U.S. Appl. No. 13/215,916, filed Aug. 23, 2011, Notice of Allowance mailed Jan. 4, 2013, 10 pages. |
U.S. Appl. No. 13/294,005, filed Nov. 11, 2011, Non-Final Office Action mailed Aug. 14, 2013, 32 pages. |
U.S. Appl. No. 13/294,005, filed Nov. 11, 2011, Final Office Action mailed Jan. 3, 2014, 29 pages. |
U.S. Appl. No. 13/592,976, filed Aug. 23, 2012, Notice of Allowance mailed Oct. 7, 2013, 18 pages. |
U.S. Appl. No. 13/797,173, filed Mar. 12, 2013, Non Final Office Action mailed May 15, 2014, 28 pages. |
U.S. Appl. No. 13/799,653, filed Mar. 13, 2013, Non Final Office Action mailed May 8, 2014, 24 pages. |
U.S. Appl. No. 13/829,350, filed Mar. 14, 2013, Non Final Office Action mailed Feb. 28, 2014, 29 pages. |
U.S. Appl. No. 13/828,001, filed Mar. 14, 2013, Notice of Allowance mailed Apr. 25, 2014, 43 pages. |
U.S. Appl. No. 13/799,719, filed Mar. 13, 2013, Non Final Office Action mailed Oct. 25, 2013, 79 pages. |
U.S. Appl. No. 13/799,719, filed Mar. 13, 2013, Notice of Allowance mailed Apr. 23, 2014, 141 pages. |
U.S. Appl. No. 14/064,423, filed Oct. 28, 2013, Non-Final Office Action mailed Dec. 20, 2013, 18 pages. |
U.S. Appl. No. 14/064,423, filed Oct. 28, 2013, Notice of Allowance mailed Mar. 4, 2013, 37 pages. |
U.S. Appl. No. 14/095,860, filed Dec. 3, 2013 Final Office Action mailed May 1, 2015, 18 pages. |
U.S. Appl. No. 14/060,388, filed Oct. 22, 2013 Notice of Allowance mailed Apr. 13, 2015, 44 pages. |
U.S. Appl. No. 13/888,012, filed May 6, 2013 Non-Final Rejection mailed Apr. 6, 2015, 36 pages. |
U.S. Appl. No. 13/801,968, filed Mar. 13, 2013 Non Final Office Action mailed May 21, 2015, 49 pages. |
U.S. Appl. No. 13/614,899, filed Sep. 13, 2012 Notice of Allowance mailed Mar. 13, 2015, 35 pages. |
U.S. Appl. No. 13/302,852, filed Nov. 22, 2011 Final Rejection mailed Mar. 30, 2015, 29 pages. |
U.S. Appl. No. 13/215,598, filed Aug 23, 2011 Final Office Action mailed May 5, 2015, 17 pages. |
European Search Report for EP 12825653 dated Mar. 11, 2015, 7 pages. |
Supplementary European Search Report for Application No. EP 12825147 dated Mar. 27, 2015, 9 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. |
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. |
The second Office Action dated Feb. 26, 2015 for Mexican Patent Application No. MX/a/2013/014217 is not translated into English, 3 pages. |
U.S. Appl. No. 14/467,959, filed Aug. 25, 2014 Notice of Allowance mailed Jun. 22, 2015, 36 pages. |
U.S. Appl. No. 14/154,887, filed Jan. 14, 2014 Non-Final Rejection mailed Jul. 17, 2015, 33 pages. |
U.S. Appl. No. 14/095,860, filed Dec. 3, 2013 Notice of Allowance mailed Jul. 13, 2015, 31 pages. |
U.S. Appl. No. 14/043,617, filed Oct. 1, 2011, Final Office Action mailed Jul. 16, 2015, 45 pages. |
U.S. Appl. No. 13/888,012, filed May 6, 2013, Notice of Allowance mailed Jul. 14, 2015, 18 pages. |
U.S. Appl. No. 13/829,350, filed Mar. 14, 2013 Notice of Allowance mailed Jul. 24, 2015, 29 pages. |
U.S. Appl. No. 13/799,604, filed Mar. 13, 2013, Notice of Allowance mailed May 29, 2015, 46 pages. |
U.S. Appl. No. 13/302,852, filed Nov. 22, 2011, Notice of Allowance mailed Jun. 19, 2015, 26 pages. |
U.S. Appl. No. 13/292,047, filed Nov. 8, 2011 Non-Final Office Action mailed Jul. 7, 2015, 28 pages. |
U.S. Appl. No. 13/288,002, filed Nov. 2, 2011 Non Final Rejection mailed Jul. 28, 2015, 29 pages. |
Supplementary European Search Report for EP 13761291.7 mailed Jul. 9, 2015, 8 pages. |
The Notice of Allowance by the Mexican Institute of Industrial Property for Mexican Patent Application No. MX/a/2013/014671 dated Apr. 17, 2015, 1 page. |
Office Action dated May 18, 2015 for Mexican Patent Application No. MX/a/2014/009776, 2 pages. |
Office Action dated May 12, 2015 for Mexican Patent Application No. MX/a/2014/009723, 2 pages. |
U.S. Appl. No. 13/757,168, filed Feb. 1, 2013 Non Final Office Action mailed Jun. 4, 2014, 23 pages. |
U.S. Appl. No. 13/799,604, filed Mar. 13, 2013 Non Final Office Action mailed Jun. 6, 2014, 24 pages. |
U.S. Appl. No. 13/614,899, filed Sep. 13, 2012 Non-Final Office Action mailed May 20, 2014, 25 pages. |
U.S. Appl. No. 13/215,598, filed Aug. 23, 2011 Final Office Action mailed Jul. 2, 2014, 22 pages. |
U.S. Appl. No. 13/294,005, filed Nov. 11, 2011 Non-Final Office Action mailed May 20, 2014, 33 pages. |
U.S. Appl. No. 13/829,350, filed Mar. 14, 2013 Non Final Office Action mailed Jul. 29, 2014, 24 pages. |
U.S. Appl. No. 13/795,914, filed Mar. 6, 2013 Notice of Allowance mailed Jul. 21, 2014, 13 pages. |
U.S. Appl. No. 13/795,914, filed Mar. 6, 2013 Final Office Action mailed Apr. 3, 2014, 17 pages. |
U.S. Appl. No. 14/340,190, filed Jul. 24, 2014 Non-Final Rejection mailed Aug. 31, 2015, 74 pages. |
U.S. Appl. No. 13/799,604, filed Mar. 13, 2013, Notice of Allowance mailed Jul. 24, 2015, 34 pages. |
Extended European Search Report for EP 13760237.1 received Jul. 21, 2015, 8 pages. |
First Office Action and Search Report from the State Intellectual Property Office (SIPO) for CN 201280031434.7, issued Jul. 17, 2015, 12 pages. |
Office Action dated Jul. 31, 2015 for Mexican Patent Application No. MX/a/2014/009928, 2 pages. |
International Search Report and Written Opinion of PCT/US2013/031432 mailed May 28, 2013, 10 pages. |
International Preliminary Report on Patentability for PCT/US2013/031432 issued Sep. 16, 2014, 9 pages. |
International Search Report and Written Opinion of PCT/US2013/031445 mailed May 24, 2013, 11 pages. |
International Preliminary Report on Patentability for PCT/US2013/031445 issued Sep. 16, 2014, 10 pages. |
U.S. Appl. No. 13/302,852, filed Nov. 22, 2011, Non-Final Rejection mailed Sep. 2, 2014, 28 pages. |
U.S. Appl. No. 13/793,636, filed Mar. 11, 2013, Non-Final Office Action mailed Sep. 29, 2014, 27 pages. |
U.S. Appl. No. 13/800,477, filed Mar. 13, 2013 Non-Final Office Action mailed Sep. 11, 2014, 34 pages. |
International Preliminary Report on Patentability for PCT/US2013/032176 mailed Sep. 25, 2014, 7 pages. |
International Preliminary Report on Patentability for PCT/US2013/031565 issued Sep. 16, 2014, 18 pages. |
International Preliminary Report on Patentability for PCT/US2013/031915 issued Sep. 16, 2014, 5 pages. |
International Search Report and Written Opinion of PCT/US2013/031440 mailed May 30, 2013, 14 pages. |
International Search Report and Written Opinion of PCT/US2013/031440 mailed Sep. 25, 2014, 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. |
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. |
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/E E-to-launch-TV-set-top-box.htm. |
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. |
International Search Report and Written Opinion of PCT/US2013/32176 mailed on Jun. 25, 2013, 15 pages. |
International Search Report and Written Opinion of PCT/US2013/031565 mailed on May 31, 2013, 103 pages. |
International Search Report and Written Opinion of PCT/US2013/031915 mailed on Jun. 3, 2013, 7 pages. |
International Search Report of PCT/KR2007/003521 mailed on Oct. 23, 2007. |
International Search Report of PCT/IB2003/005737 mailed on Mar. 3, 2004. |
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. |
Extended European Search Report for EP 12825080 mailed Sep. 11, 2014, 10 pages. |
Extended European Search Report for EP 12825521 mailed Nov. 24, 2014, 7 pages. |
U.S. Appl. No. 14/095,860, filed Dec. 3, 2013 Non-Final Office Action mailed Dec. 26, 2014, 45 pages. |
U.S. Appl. No. 14/043,617, filed Oct. 1, 2013 Non-Final Office Action mailed Jan. 5, 2014, 45 pages. |
U.S. Appl. No. 13/856,752, filed Apr. 4, 2013 Non Final Office Action mailed Nov. 5, 2014, 34 pages. |
U.S. Appl. No. 13/829,350, filed Mar. 14, 2013 Final Office Action mailed Jan. 23, 2015, 18 pages. |
U.S. Appl. No. 13/799,653, filed Mar. 13, 2013 Notice of Allowance mailed Nov. 26, 2014, 32 pages. |
U.S. Appl. No. 13/799,604, filed Mar. 13, 2013, Final Office Action mailed Jan. 14, 2015, 36 pages. |
U.S. Appl. No. 13/797,173, filed Mar. 12, 2013 Notice of Allowance mailed Nov. 24, 2015, 37 pages. |
U.S. Appl. No. 13/757,168, filed Feb. 1, 2013 Notice of Allowance mailed Oct. 14, 2015, 28 pages. |
U.S. Appl. No. 13/294,005, filed Nov. 11, 2013 Notice of Allowance mailed Oct. 31, 2014, 24 pages. |
U.S. Appl. No. 13/292,047, filed Nov. 8, 2013 Final Office Action mailed Jan. 13, 2015, 22 pages. |
U.S. Appl. No. 13/215,598, filed Aug. 23, 2013 Non-Final Office Action mailed Nov. 25, 2014, 18 pages. |
U.S. Appl. No. 13/786,915, filed Mar. 6, 2013 Non Final Rejection mailed Oct. 15, 2015, 59 pages. |
U.S. Appl. No. 14/095,860, filed Dec. 3, 2013 Notice of Allowance mailed Oct. 19, 2015, 14 pages. |
U.S. Appl. No. 14/338,114, filed Jul. 22, 2014 Non-Final Office Action mailed Sep. 30, 2015, all pages. |
U.S. Appl. No. 14/529,989, filed Oct. 31, 2014 Non-Final Office Action mailed Nov. 4, 2015, all pages. |
U.S. Appl. No. 14/043,617, filed Oct. 1, 2013 Non-Final Office Action mailed Oct. 23, 2015, all pages. |
U.S. Appl. No. 14/676,137, filed Apr. 1, 2015 Notice of Allowance mailed Sep. 28, 2015, 35 pages. |
Supplementary European Search Report for EP 13760902 mailed Oct. 20, 2015, all pages. |
Supplementary European Search Report for EP 13761427 mailed Oct. 19, 2015, all pages. |
Office Action dated Jul. 31, 2015 for Mexican Patent Application No. MX/a/2014/009919, 2 pages. |
U.S. Appl. No. 14/340,190, filed Jul. 24, 2014, Final Rejection mailed Feb. 19, 2016, 54 pages. |
U.S. Appl. No. 14/154,887, filed Jan. 14, 2014 Notice of Allowance mailed Jan. 21, 2016, 26 pages. |
U.S. Appl. No. 13/288,002, filed Nov. 2, 2011 Final Rejection mailed Jan. 13, 2016, 22 pages. |
U.S. Appl. No. 13/292,047, filed Nov. 8, 2011 Notice of Allowance mailed Jan. 29, 2016, 45 pages. |
U.S. Appl. No. 13/215,598, filed Aug 23, 2011 Non Final Office Action mailed Dec. 15, 2015, all pages. |
U.S. Appl. No. 13/801,968, filed Mar. 13, 2013 Final Office Action mailed Nov. 19, 2015, all pages. |
U.S. Appl. No. 14/589,090, Notice of Allowance mailed Feb. 9, 2016, 47 pages. |
U.S. Appl. No. 14/591,549, Non Final Office Action mailed Dec. 31, 2015, 19 pages. |
U.S. Appl. No. 14/338,114, filed Jul. 22, 2014 Notice of Allowance mailed Feb. 3, 2016, all pages. |
Second Office Action for CN 201280031434.7, issued Dec. 23, 2015, 6 pages. |
First Office Action issued by State Intellectual Property Office (SIPO) for CN 201280028697.2, issued Dec. 16, 2015, 11 pages. |
Notice of Allowance received for Mexican Patent Appln. MX/a/2013/014991, mailed on Dec. 9, 2015, 1 page. |
Notice of Allowance mailed Dec. 4, 2015 for Mexican Patent Application No. MX/a/2014/009723, 1 page. |
International Search Report and Written Opinion of PCT/US2015/065934 mailed Apr. 8, 2016, all pages. |
International Search Report and Written Opinion of PCT/EP2015/073937 mailed Apr. 15, 2016, all 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 Final Rejection mailed May 12, 2016, 27 pages. |
U.S. Appl. No. 13/786,915, filed Mar. 6, 2013 Notice of Allowance mailed Jul. 19, 2016, all pages. |
U.S. Appl. No. 14/757,606, filed Dec. 23, 2015 Non Final Rejection mailed Mar. 24, 2016, 33 pages. |
U.S. Appl. No. 13/786,915, filed Dec. 23, 2015, Notice of Allowance mailed Jul. 18, 2016, all pages. |
U.S. Appl. No. 13/215,598, filed Aug. 23, 2011 Notice of Allowance mailed May 24, 2016, all pages. |
U.S. Appl. No. 13/801,968, filed Mar. 13, 2013 Notice of Allowance mailed Apr. 27, 2016, 33 pages. |
U.S. Appl. No. 14/591,549, Final Office Action mailed Jun. 30, 2016, all pages. |
U.S. Appl. No. 14/529,989, filed Oct. 31, 2014 Final Rejection mailed May 6, 2016, 27 pages. |
U.S. Appl. No. 14/043,617, filed Oct. 1, 2013 Final Office Action mailed May 6, 2016, 56 pages. |
Office Action for European Application No. 12825147 dated Mar. 7, 2016, all pages. |
Decision to Grant from the State Intellectual Property Office (SIPO) for CN 201280031434.7, issued May 12, 2016, all pages. (in Chinese language). |
Notice of Allowance dated Jan. 15, 2016 for Mexican Patent Application No. MX/a/2014/009928, 1 page. |
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. |
Notice of Allowance dated Dec. 16, 2015 for Mexican Patent Application No. MX/a/2014/009919 1 page. |
Author Unknown, “Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB systems,” ETSI EN 300 468 V1.1 (Jan. 2013), 172 pages. |
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, issued Aug. 3, 2016, 10 pages. |
First Office Action and Search Report for CN Appin No. 201280030476.9 issued Aug. 9, 2016, all pages. |
Number | Date | Country | |
---|---|---|---|
20130243398 A1 | Sep 2013 | US |
Number | Date | Country | |
---|---|---|---|
61611483 | Mar 2012 | US |