The advent of the digital video recorder (DVR) and the availability of high-capacity computer-readable storage devices at reasonable prices have made available many possibilities to television programming service providers and television viewers alike. In recent years, television viewers have come to expect the ability to easily customize and manage the recording of television programming via their television receivers.
In some embodiments, a television receiver system for successive initialization of television channel recording may be presented. The system may include a control processor. The control processor may be configured to determine a plurality of television channels are configured to begin recording at a same time. The control processor may be configured to transmit, to a tuning management processor, a first request for recording of a first television channel of the plurality of television channels. The control processor may be configured to in response to receiving an acknowledgement, transmit, to the tuning management processor, a second request for recording of a second television channel of the plurality of television channels. The system may include a tuning management processor. The tuning management processor may be configured to configure a first recording of the first television channel in response to the first request. The tuning management processor may be configured to transmit the acknowledgement to the control processor following the first recording of the first television channel being configured. The tuning management processor may be configured to cause the first television channel to be recorded to a file.
Embodiments of such a system may include one or more of the following: The television receiver system may include a tuner, wherein each television channel of the plurality of television channels is tuned to using the tuner. The tuning management processor may be configured to configure the first recording of the first television channel in response to the first request may include the tuning management processor being configured to tune the tuner to a frequency of a transponder stream, wherein the plurality of television channels are transmitted as part of the transponder stream. The tuning management processor may be configured to initiate a first packet identifier filter for a first packet identifier to capture program data from the transponder stream, wherein the program data indicates packet identifiers of video streams and audio streams of the plurality of television channels. The tuning management processor being configured to configure the first recording of the first television channel in response to the first request may include the tuning management processor being configured to use the program data captured using the first packet identifier filter to determine a second packet identifier and a third packet identifier associated with the first television channel. The tuning processor may be configured to initiate a second packet identifier filter to capture audio data and video data from the transponder stream for the first television channel. The second packet identifier filter may filter based on the second packet identifier and the third packet identifier.
Additionally or alternatively, embodiments of such a system may include one or more of the following: The tuning management processor may be configured to configure a second recording of the second television channel in response to the second request. Configuring the second recording of the second television channel may include the tuning management processor being configured to use the program data captured using the first packet identifier filter to determine a fourth packet identifier and a fifth packet identifier associated with the second television channel; and initiate a third packet identifier filter to capture audio data and video data from the transponder stream for the second television channel, wherein the third packet identifier filter filters using the fourth packet identifier and the fifth packet identifier. The tuning management processor may be further configured to transmit a second acknowledgement to the control processor following the second recording of the second television channel being configured. The television receiver system may be configured to receive an indication of the plurality of television channels to be simultaneously recorded for a period of time from a television service provider via satellite.
In some embodiments, a method for successive initialization of television channel recording may be presented. The method may include determining, by a control processor of a television receiver, a plurality of television channels are configured to begin recording at a same time. The method may include transmitting, by the control processor to a tuning management processor of the television receiver, a first request for reception of a first television channel of the plurality of television channels. The method may include configuring, by the tuning management processor, a first recording of the first television channel in response to the first request. The method may include causing, by the tuning management processor, the first television channel to be recorded to a file. The method may include transmitting, by the tuning management processor to the control processor, an acknowledgement to the control processor following the first recording of the first television channel being configured. The method may include, in response to receiving the acknowledgement, transmitting, by the control processor to the tuning management processor, a second request for reception of a second television channel of the plurality of television channels.
Embodiments of such a method may include one or more of the following: The method may include tuning, using a tuner of the television receiver, to each television channel of the plurality of television channels. Configuring the first recording of the first television channel in response to the first request may include: tuning the tuner to a frequency of a transponder stream, wherein the plurality of television channels are transmitted as part of the transponder stream; and initiating a first packet identifier filter for a first packet identifier to capture program data from the transponder stream, wherein the program data indicates packet identifiers of video streams and audio streams of the plurality of television channels. Configuring the first recording of the first television channel in response to the first request may include: using the program data captured using the first packet identifier filter to determine a second packet identifier and a third packet identifier associated with the first television channel; and initiating a second packet identifier filter to capture audio data and video data from the transponder stream for the first television channel. The second packet identifier filter may filter based on the second packet identifier and the third packet identifier.
Additionally or alternatively, embodiments of such a method may include one or more of the following: The method may include configuring a second recording of the second television channel in response to the second request. Configuring the second recording of the second television channel may include: using the program data captured using the first packet identifier filter to determine a fourth packet identifier and a fifth packet identifier associated with the second television channel; and initiating a third packet identifier filter to capture audio data and video data from the transponder stream for the second television channel. The third packet identifier filter may filter using the fourth packet identifier and the fifth packet identifier. The method may include transmitting, by the tuning management processor, a second acknowledgement to the control processor following the second recording of the second television channel being configured. The method may include receiving, by the television receiver, an indication of the plurality of television channels to be simultaneously recorded for a period of time from a television service provider via satellite.
In some embodiments, an apparatus for successive initialization of television channel recording is presented. The apparatus may include means for determining a plurality of television channels are configured to begin recording at a same time. The apparatus may include means for transmitting a first request for reception of a first television channel of the plurality of television channels. The apparatus may include means for configuring a first recording of the first television channel in response to the first request. The apparatus may include means for causing the first television channel to be recorded to a file. The apparatus may include means for transmitting an acknowledgement following the first recording of the first television channel being configured. The apparatus may include means for transmitting, in response to receiving the acknowledgement, a second request for reception of a second television channel of the plurality of television channels.
Embodiments of such an apparatus may include one or more of the following: The apparatus may include means for tuning to each television channel of the plurality of television channels. The means for configuring the first recording of the first television channel in response to the first request may include: means for tuning to a frequency of a transponder stream, wherein the plurality of television channels are transmitted as part of the transponder stream; and means for initiating a first packet identifier filter for a first packet identifier to capture program data from the transponder stream, wherein the program data indicates packet identifiers of video streams and audio streams of the plurality of television channels. The means for configuring the first recording of the first television channel in response to the first request may include means for using the program data captured using the first packet identifier filter to determine a second packet identifier and a third packet identifier associated with the first television channel; and means for initiating a second packet identifier filter to capture audio data and video data from the transponder stream for the first television channel, wherein the second packet identifier filter filters based on the second packet identifier and the third packet identifier.
Additionally or alternatively, embodiments of such an apparatus may include one or more of the following: The apparatus may include means for configuring a second recording of the second television channel in response to the second request. The means for configuring the second recording of the second television channel may include: means for using the program data captured using the first packet identifier filter to determine a fourth packet identifier and a fifth packet identifier associated with the second television channel; and means for initiating a third packet identifier filter to capture audio data and video data from the transponder stream for the second television channel. The third packet identifier filter may filter using the fourth packet identifier and the fifth packet identifier. The apparatus may include means for transmitting a second acknowledgement following the second recording of the second television channel being configured.
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. If 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.
A television viewer, referred to as a user, may use a stand-alone or integrated digital video recorder (DVR) to record broadcast television programming for viewing at a later time. In some situations, individual television programs may be recorded; in other situations, a television channel may be recorded for a period of time, such as during primetime (which may be from 8-10 PM, 7-9 PM, 7-10 PM, etc.). The recording of a television channel for such a period of time may be defined by the television service provider. During this period of time which the television channel is recorded, multiple television programs may be broadcast on the television channel. For example, sitcoms may tend to be scheduled for thirty minutes, including commercials; dramas may tend to be scheduled for an hour including commercials. Recording of a television channel, such as during primetime, for multiple hours may result in two or more, possibly six, television programs being recorded.
In some embodiments, 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 any television program that was broadcast during primetime on one of the major networks at a later time. When multiple television channels are recorded simultaneously, in some embodiments it is efficient to use a single tuner to receive all of the multiple television channels being recorded. This allows other tuners of the television receiver to be used for other operations (e.g., recording of other television channels and/or presentation of television channels to a user via a viewing device, such as a television).
When multiple television channels are scheduled to begin being recorded at a same time (e.g., each major network being scheduled to begin being recorded at 7 PM), various (e.g., hardware, firmware, software) limitations may prevent recording of both television channels from being initiated at precisely the same time. Rather than beginning recording at the same time, requests to begin recording may be sent separately to a component of the television receiver that handles the recording, with a second request being held until an acknowledgement from the component is received that indicates recording in accordance with a first request has successfully been initiated. For example, a control processor may manage a determination of which channels are scheduled] [??] and at what time recording of the television channels is to occur. A tuning management processor may handle the specifics of recording, including tuning a tuner to the proper frequency to receive the television channels, determining packet identifiers (PIDs) of the television channels to be recorded, filtering a received transponder stream by PID, and storing the recording of each television channel to an individual file.
Television service provider system 110 and satellite transmitter equipment 120 may be operated by a television service provider. A television service provider may distribute television channels, on-demand programming, programming information, and/or other services to users. Television service provider system 110 may receive feeds of one or more television channels from various sources. Such television channels may include multiple television channels that contain the same content (but may be in different formats, such as high-definition and standard-definition). To distribute such television channels to users, feeds of the television channels may be relayed to user equipment via one or more satellites via transponder streams. Satellite transmitter equipment 120 may be used to transmit a feed of one or more television channels from television service provider system 110 to one or more satellites 130. While a single television service provider system 110 and satellite transmitter equipment 120 are illustrated as part of satellite television distribution system 100, it should be understood that multiple instances of transmitter equipment may be used, possibly scattered geographically to communicate with satellites 130. Such multiple instances of satellite transmitting equipment may communicate with the same or with different satellites. Different television channels may be transmitted to satellites 130 from different instances of transmitting equipment. For instance, a different satellite dish of satellite transmitter equipment 120 may be used for communication with satellites in different orbital slots.
Satellites 130 may be configured to receive signals, such as streams of television channels, from one or more satellite uplinks such as satellite transmitter equipment 120. Satellites 130 may relay received signals from satellite transmitter equipment 120 (and/or other satellite transmitter equipment) to multiple instances of user equipment via transponder streams. Different frequencies may be used for uplink signals 170 from transponder stream 180. Satellites 130 may be in geosynchronous orbit. Each satellite 130 may be in a different orbital slot, such that the signal paths between each satellite, transmitter equipment, and user equipment vary. Multiple satellites 130 may be used to relay television channels from television service provider system 110 to satellite dish 140. Different television channels may be carried using different satellites. Different television channels may also be carried using different transponders of the same satellite; thus, such television channels may be transmitted at different frequencies and/or different frequency ranges. As an example, a first and second television channel may be carried on a first transponder of satellite 130-1. A third, fourth, and fifth television channel may be carried using a different satellite or a different transponder of the same satellite relaying the transponder stream at a different frequency. A transponder stream transmitted by a particular transponder of a particular satellite may include a finite number of television channels, such as seven. Accordingly, if many television channels are to be made available for viewing and recording, multiple transponder streams may be necessary to transmit all of the television channels to the instances of user equipment.
Satellite dish 140 may be a piece of user equipment that is used to receive transponder streams from one or more satellites, such as satellites 130. Satellite dish 140 may be provided to a user for use on a subscription basis to receive television channels provided by the television service provider system 110, satellite transmitter equipment 120, and/or satellites 130. Satellite dish 140 may be configured to receive transponder streams from multiple satellites and/or multiple transponders of the same satellite. Satellite dish 140 may be configured to receive television channels via transponder streams on multiple frequencies. Based on the characteristics of television receiver 150 and/or satellite dish 140, it may only be possible to capture transponder streams from a limited number of transponders concurrently. For example, a tuner of television receiver 150 may only be able to tune to a single transponder stream from a transponder of a single satellite at a time.
In communication with satellite dish 140 may be one or more sets of receiving equipment. Receiving equipment may be configured to decode signals received from satellites 130 via satellite dish 140 for display on a display device, such as television 160. Receiving equipment may be incorporated as part of a television or may be part of a separate device, commonly referred to as a set-top box (STB). Receiving equipment may include a satellite tuner configured to receive television channels via a satellite. In
Television 160 may be used to present video and/or audio decoded by television receiver 150. Television receiver 150 may also output a display of one or more interfaces to television 160, such as an electronic programming guide (EPG). In some embodiments, a display device other than a television may be used.
Uplink signal 170-1 represents a signal between satellite transmitter equipment 120 and satellite 130-1. Uplink signal 170-2 represents a signal between satellite transmitter equipment 120 and satellite 130-2. Each of uplink signals 170 may contain streams of one or more different television channels. For example, uplink signal 170-1 may contain a certain group of television channels, while uplink signal 170-2 contains a different grouping of television channels. Each of these television channels may be scrambled such that unauthorized persons are prevented from accessing the television channels.
Transponder stream 180-1 represents a signal between satellite 130-1 and satellite dish 140. Transponder stream 180-2 represents a signal path between satellite 130-2 and satellite dish 140. Each of transponder streams 180 may contain one or more different television channels in the form of transponder streams, which may be at least partially scrambled. For example, transponder stream 180-1 may include a first transponder stream containing a first group of television channels, while transponder stream 180-2 may include a second transponder stream containing a different group of television channels. A satellite may transmit multiple transponder streams to user equipment. For example, a typical satellite may relay thirty-two transponder streams via corresponding transponders to user equipment. Further, spot beams are possible. For example, a satellite may be able to transmit a transponder stream to a particular geographic region (e.g., to distribute local television channels to the relevant market). Different television channels may be transmitted using the same frequency of the transponder stream to a different geographic region.
Network 190 may serve as a secondary communication channel between television service provider system 110 and television receiver 150. Via such a secondary communication channel, bidirectional exchange of data may occur. As such, data may be transmitted to television service provider system 110 via network 190. Data may also be transmitted from television service provider system 110 to television receiver 150 via network 190. Network 190 may be the Internet. While audio and video services may be provided to television receiver 150 via satellites 130, feedback from television receiver 150 to television service provider system 110 may be transmitted via network 190.
Processors 210 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 EPG database 230, and/or receiving and processing input from a user. For example, processors 210 may include one or more processors dedicated to decoding video signals from a particular format, such as MPEG, for output and display on a television and for performing decryption. It should be understood that the functions performed by various modules of
Control processor 210-1 may communicate with tuning management processor 210-2. Control processor 210-1 may control the recording of television channels based on timers stored in DVR database 245. In some embodiments timers are stored in some other database or storage arrangement. Control processor 210-1 may initiate recording of a television channel by sending a record command along with an indication of the television channel to be recorded to tuning management processor 210-2. Control processor 210-1 may not send a second record command (if 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 tuning management processor 210-2. Control processor 210-1 may also provide commands to tuning management processor 210-2 when recording of a television channel is to cease. In addition to providing commands relating to the recording of television channels, control processor 210-1 may provide commands to tuning management processor 210-2 that indicate television channels to be output to audio/video decoder 233 for output to a presentation device, such as a television.
Control processor 210-1 may also communicate with network interface 220 and user interface 250. Control processor 210-1 may handle in-coming data from network interface 220 and user interface 250. Additionally, control processor 210-1 may be configured to output data via network interface 220.
Tuners 215 may include one or more tuners used to tune to television channels, such as television channels transmitted via satellite or cable. In the illustrated embodiment of television receiver 200, three tuners are present (tuner 215-1, tuner 215-2, and tuner 215-3). Each tuner contained in tuners 215 may be capable of receiving and processing a transport stream of data from a satellite transponder (or a cable RF channel) at a given time. This transport stream may contain audio and video data for multiple television channels in addition to other data. As such, a single tuner may tune to a single transponder (or, for a cable network, a single cable RF channel). If tuners 215 include multiple tuners, one tuner may be used to tune to a television channel on a first transponder stream for display using a television, while another tuner may be used to tune to a television channel on a second transponder for recording and viewing at some other time. If multiple television channels transmitted on the same transponder stream are desired, a single tuner of tuners 215 may be used to receive the signal containing the multiple television channels for presentation and/or recording. Tuners 215 may receive commands from tuning management processor 210-2. Such commands may instruct tuners 215 which frequencies are to be used for tuning.
Network interface 220 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. Referring back to
Storage medium 225 may represent a non-transitory computer-readable storage medium. Storage medium 225 may include memory and/or a hard drive. Storage medium 225 may be used to store information received from one or more satellites and/or information received via network interface 220. Storage medium 225 may store information related to EPG database 230, and/or DVR database 245. In some embodiments, storage medium 225 may also be used to store various tables, such as NIT 240, PMT 257, and/or PAT. Recorded television programs may be stored using storage medium 225. Storage medium 225 may be partitioned or otherwise divided such that predefined amounts of storage medium 225 are devoted to storage of omnibus channel files and user-selected television programs. Storage medium 225 may be at least partially organized as a service descriptor table, which may be persistent or fetched as needed.
EPG database 230 may store information related to television channels and the timing of programs appearing on such television channels. EPG database 230 may be stored using storage medium 225, which may be a hard drive. Information from EPG database 230 may be used to inform users of what television channels or programs are popular and/or provide recommendations to the user. Information from EPG database 230 may provide the user with a visual interface 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 EPG database 230 may be received via network interface 220 and/or via satellites, such as satellites 130 of
In addition to being used to provide users with information about scheduled programming, information from EPG database 230 may be used to determine when television programs begin and end for the purposes of recording. For instance, if a channel-specific file is recorded that contains multiple television programs, 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. Other data may be stored for the EPG 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).
Audio/video decoder 233 may serve to convert encoded video and audio into a format suitable for output to a display device. For instance, audio/video decoder 233 may receive MPEG video and audio from storage medium 225 or descrambling engine 265 to be output to a television. MPEG video and audio from storage medium 224 may have been recorded to DVR database 245 as part of a previously-recorded television program. Audio/video decoder 233 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.
Television interface 235 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, television interface 235 may output one or more television channels, stored television programming from storage medium 225 (e.g., television programs from DVR database 245 and/or information from EPG database 230) to a television for presentation.
The Network Information Table (NIT) 240 may store information used by television receiver 200 to access various television channels. NIT 240 may be stored locally by a processor, such as by tuning management processor 210-2. Information used to populate NIT 240 may be received via satellite (or cable) through tuners 215 and/or may be received via network interface 220 from the television service provider. As such, information present in NIT 240 may be periodically updated. In some embodiments, NIT 240 may be locally-stored by television receiver 200 using storage medium 225. Generally, NIT 240 may store information about a service provider network, such as a satellite-based service provider network. Information that may be present in NIT 240 may include: television channel numbers, satellite identifiers, frequency identifiers and/or transponder identifiers for various television channels. In some embodiments, NIT 240 may contain additional data or additional tables may be stored by the television receiver. For example, specific audio PIDs and video PIDs may not be present in NIT 240, a channel identifier may be present within NIT 240 which may be used to look up the audio PIDs and video PIDs in another table, such as a program map table (PMT). In some embodiments, a PID associated with the data for the PMT is indicated in a separate table, program association table (PAT), which is not illustrated in
Table 1 provides a simplified example of NIT 240 for several television channels. It should be understood that in other embodiments, many more television channels may be represented in NIT 240. NIT 240 may be periodically updated by a television service provider. As such, television channels may be reassigned to different satellites and/or transponders, and television receiver 200 may be able to handle this reassignment as long as NIT 240 is updated.
Based on information in the NIT, 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 may list a particular frequency to which to tune for a particular television channel. Once tuned to the proper satellite/transponder/frequency, a known PMT PID may be used to retrieve a program map 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 240. Additional information on how NIT 240, as indicated in Table 1, may be used is provided in reference to
A Digital Video Recorder (DVR) may permit a television channel to be recorded for a period of time. DVR functionality of television receiver 200 may be managed by control processor 210-1. Control processor 210-1 may coordinate the television channel, start time, and stop time of when recording of a television channel is to occur. DVR database 245 may store information related to the recording of television stations. DVR database 245 may store timers that are used by control processor 210-1 to determine when a television channel should be tuned to and its programs recorded to DVR database 245 of storage medium 225. In some embodiments, timers are stored in another storage arrangement. For example, one or more timer files may be stored using the storage medium that indicate a television channel and a date/time period during which recording should be performed. In some embodiments, a limited amount of storage medium 225 may be devoted to DVR database 245. Timers may be set by the television service provider and/or one or more users of television receiver 200.
The DVR functionality of control processor 210-1 may have multiple modes. First, the DVR functionality of control processor 210-1 may be configured to record individual television programs selected by a user to DVR database 245. Using EPG database 230, a user may select a particular television program. Based on the date, time period, and television channel indicated by EPG database 230, Control processor 210-1 may record the associated television program to DVR database 245. Second, DVR database 245 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 the television service provider.
As an example of this second mode of DVR functionality, a television service provider may configure television receiver 200 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 television receiver 200 such that television programming may be recorded from 7 to 10 PM on NBC, ABC, CBS, and FOX on each weeknight. If 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).
User interface 250 may include a remote control (physically separate from television receiver 200) and/or one or more buttons on television receiver 200 that allows a user to interact with television receiver 200. User interface 250 may be used to select a television channel for viewing, view information from EPG database 230, and/or program a timer stored to DVR database 245, wherein the timer is used to control the DVR functionality of control processor 210-1.
Referring back to tuners 215, 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 (e.g., nonsubscribers) from receiving television programming without paying the television service provider. When a tuner of tuners 215 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 packet identifier (PID), which, in combination with NIT 240 and/or PMT 257, can be determined to be associated with particular television channel. Particular data packets, referred to as entitlement control messages (ECMs) may be periodically transmitted. ECMs may be associated with another PID and may be encrypted; television receiver 200 may use smart card 260 to decrypt ECMs. Decryption of an ECM may only be possible if the user 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 smart card 260 for decryption.
When smart card 260 receives an encrypted ECM, smart card 260 may decrypt the ECM to obtain some number of control words. In some embodiments, from each ECM received by smart card 260, two control words are obtained. In some embodiments, when smart card 260 receives an ECM, it compares the ECM to the previously received ECM. If 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 smart card 260 is decrypted; however, if 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 smart card 260. Smart card 260 may be permanently part of television receiver 200 or may be configured to be inserted and removed from television receiver 200.
Tuning management processor 210-2 may be in communication with tuners 215 and control processor 210-1. Tuning management processor 210-2 may be configured to receive commands from control processor 210-1. 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. Tuning management processor 210-2 may control tuners 215. Tuning management processor 210-2 may provide commands to tuners 215 that instruct the tuners which satellite, transponder, and/or frequency to tune to. From tuners 215, tuning management processor 210-2 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.
Tuning management processor 210-2 may be configured to create one or more PID filters 255 that sort packets received from tuners 215 based on the PIDs. When a tuner is initially tuned to a particular frequency (e.g., to 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 NIT 240 or another table, such as a PAT. From the PMT data packets, PMT may be constructed by tuning management processor 210-2. Table 2 provides an exemplary extract of a PMT. PMT 257 may be specific to a particular transponder. As such, if tuning to a different transponder occurs, a new PMT may be created for the different transponder.
Accordingly, based on the information present in PMT 257, 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 (SAP), 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 PMT 257.
PID filters 255 may be configured to filter data packets based on PIDs. In some embodiments, PID filters 255 are created and executed by tuning management processor 210-2. In other embodiments, separate hardware may be used to create and execute such 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 PMT 257). For example, if 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 255. 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 descrambling engine 265 or smart card 260; 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 NIT 240, may be appropriately routed by PID filters 255. At a given time, one or multiple PID filters may be executed by tuning management processor 210-2.
Descrambling engine 265 may use the control words output by smart card 260 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 tuners 215 may be scrambled. Video and/or audio data may be descrambled by descrambling engine 265 using a particular control word. Which control word output by smart card 260 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 descrambling engine 265 to storage medium 225 for storage (in DVR database 245) and/or to audio/video decoder 233 for output to a television or other presentation equipment via television interface 235.
For simplicity, television receiver 200 of
Various methods may be performed in conjunction with a television distribution system (e.g., satellite-based, cable-based, IP-based) and a television receiver.
Method 300 may be useful to successively initiate recording of multiple television channels which are configured to begin recording at the same time. For example, a television service provider may configure a television receiver to record multiple television channels over the same period of time each weekday night. As a more specific example, each major television network, such as ABC, CBS, NBC, and FOX, may be recorded Monday through Friday from 7 PM until 10 PM each night. Accordingly, at 7 PM, each of these four television channels may be configured to begin being recorded. In some embodiments, each of these four television channels is received by a single tuner of the television receiver via a single transponder stream. As such, a single tuner may be used to receive multiple television channels on the single transponder stream.
At step 310, a determination may be made that the multiple television channels are scheduled to begin recording at a same time. This determination may be made by a control processor, such as control processor 210-1 of television receiver 200 of
Following the multiple television channels that are scheduled to be recorded at the same time being determined at step 310, a request for recording/reception of the first television channel may be created and provided to another processor that is configured to handle the specifics of television channel recording at step 320. Such a request may indicate the television channel to be recorded. For example, a channel number may be provided as the indication of the first television channel to be recorded. In some embodiments, a television channel name or some other form of identifier may be used to indicate the television channel to be recorded. Such a request may be provided by control processor 210-1 to another processor, such as tuning management processor 210-2 of television receiver 200. Tuning management processor 210-2 may handle the specifics of tuning to the first television channel and filtering audio, video, and encryption packets associated with the first television channel. Once the request of step 320 is sent by the control processor to the tuning management processor, despite an additional television channel being scheduled to begin recording at the same time, a request for the second television channel to be recorded may not be sent until an acknowledgement is received by the control processor from the tuning management processor that indicates recording of the first television channel has been configured.
At step 330, recording of the first television channel may be configured. Configuring of recording of the first television channel may be performed by the tuning management processor in response to the request being received at step 320 from the control processor. Configuring recording of the first television channel may include tuning a tuner of the television receiver to an appropriate frequency to receive the television channel indicated in the request received at step 320. Referring to
Configuration of the first television channel for recording may also include tuning management processor 210-2 creating and storing a program map table (PMT) that identifies the audio and video PIDs for some or all television channels transmitted as part of the transponder stream on the frequency to which tuner 215-1 is now tuned. The PMT may be constructed by creating a PID filter that filters packets having a PID associated with the PMT as indicated in an NIT or PAT stored locally by the television receiver. Configuration of recording of the first television channel may also include determining the audio and video PIDs associated with the first television channel using the PMT constructed for the transponder stream. A PID filter may be created for the audio and video PIDs associated with the first television channel. If multiple audio PIDs are available for the television channel, packets associated with one or both of the audio PIDs may be filtered by the PID filter. The filtered audio and video data packets may be stored to a file in a DVR database, such as DVR database 245 of television receiver 200.
Following configuration of the recording of the first television channel being completed, an acknowledgment may be created and transmitted to the control processor that indicates configuration of recording of the first television channel has occurred at step 340. The acknowledgement received by the control processor at step 340 may be received from the tuning management processor, such as tuning management processor 210-2 of television receiver 200. At this point in method 300, recording of the first television channel to a file may have commenced.
In response to receiving the acknowledgment at step 340, the control processor may provide a request for recording/reception of a second television channel of the multiple television channels determined at step 310. The request provided at step 350 may be created by the control processor and sent to the tuning management processor. The request sent at step 350 may be in the same format as the request sent at step 320, but may instead indicate recording of the second television channel is to commence. This second television channel of the multiple television channels may be transmitted as part of the same transponder stream as the first television channel.
At step 360, recording of the second television channel may be configured. Configuring of recording of the second television channel may be performed by the tuning management processor in response to the second request being received at step 350 from the control processor. If the second television channel is transmitted as part of the same transponder stream by the television service provider, there may be no need to tune an additional tuner and/or create a PMT based on the request to record the second television channel. Configuration to record the second television channel may include creating an additional PID filter that filters the audio and video packets associated with the second television channel and causes audio and video data for the second television channel to be stored to a second file. As such, a first file may be created and stored for the first television channel while a second file is created and stored for the second television channel. Recording to both of these files may happen during a time period.
It should be understood that, similar to step 340, an acknowledgement may be provided by the tuning management processor to the control processor following successful configuration of recording of the second television channel. If additional television channels are to be recorded, method 300 may repeat a number of times as necessary.
At step 405, indications of multiple television channels to be recorded at the same time for a period of time may be received. These indications may be received from a user and/or from a television service provider. The multiple television channels to be recorded may each be transmitted using a same transponder stream. As such, each of the television channels may be transmitted to the television receiver performing method 400 via a particular transponder of a satellite. Accordingly, following step 405, the television receiver may store indications for multiple television channels that indicate timers that indicate multiple television channels are to be recorded starting at the same time. Such timers may be stored in a DVR database.
At step 410, at or near the start time indicated by the timers, a determination may be made that the multiple television channels are scheduled to begin recording at a same time. This determination may be made by a control processor, such as control processor 210-1 of television receiver 200 of
Following the multiple television channels that are scheduled to be recorded at the same time being determined at step 410, a request for recording of the first television channel may be created and provided to another processor that is configured to handle the specifics of television channel recording at step 415. Such a request may indicate the first television channel of the multiple television channels to be recorded and/or received (e.g., tuned to). For example, a channel number may be provided as the indication of the first television channel to be recorded. In some embodiments, a television channel name or some other form of identifier may be used to indicate the television channel to be recorded. Such a request may be provided by control processor 210-1 to another processor, such as tuning management processor 210-2 of television receiver 200. Tuning management processor 210-2 may handle the specifics of tuning to the first television channel and filtering audio, video, and encryption packets associated with the first television channel. Once the request of step 320 is sent by the control processor to the tuning management processor, despite one or more additional television channels being scheduled to begin recording at the same time, a request for the second television channel to be recorded may not be sent until an acknowledgement is received by the control processor from the tuning management processor that indicates recording of the first television channel has been configured.
At step 420, recording of the first television channel may be configured. Configuring of recording of the first television channel may be performed by the tuning management processor in response to the request being received at step 415 from the control processor. Configuring recording of the first television channel by the tuning management processor may involve multiple steps. Such multiple steps are shown in
At step 421, configuring recording of the first television channel may include tuning a tuner of the television receiver to an appropriate frequency to receive the television channel indicated in the request received at step 415. Referring to
At step 422, configuration of the first television channel for recording may include tuning management processor 210-2 creating and executing a PID filter for PMT data transmitted as part of the transponder stream to which the tuner tuned at step 421. The tuning management processor may create a PID filter based on a PID indicated in an NIT or PAT stored by the television receiver. Data packets having this PID may be filtered from the transponder stream and used to create a PMT. The PMT may identify the audio and video PIDs for some or all of the television channels transmitted as part of the transponder stream on the frequency to which tuner 215-1 is now tuned. Accordingly, if each of the multiple television channels is transmitted as part of the transponder stream, the audio and video PID information for each of these television channels may be indicated in the PMT created at step 422. Following step 422, the PMT for the transponder stream to which a tuner is tuned at step 421 may be constructed.
At step 423, the PIDs for the audio and video of the first television channel may be determined using the PMT constructed at step 422. By using the PMT, the PIDs associated with the first television channel to be recorded can be determined. In addition to PIDs for the audio and video of the first television channel being identified using the PMT at step 423, PIDs for other data related to the first television channel, such as ECMs related to the first television channel, may be identified.
At step 424, a PID filter may be created and initialized for the audio and video packets associated with the first television channel. The PIDs used for the PID filter may be based on the PIDs identified at step 423. Therefore, the PID filter created at step 424 may filter audio, video, and/or other data (e.g., ECMs) related to the first television channel. The audio, video, and/or other data may begin being recorded for the first television channel to a file at step 425. Such recording may continue until the command is received by the tuning management processor that indicates recording of the television channel is to cease. Following step 425, configuration of recording the first television channel may be considered complete.
Following configuration of the recording of the first television channel being completed, an acknowledgment may be created and transmitted to the control processor that indicates configuration of recording of the first television channel has occurred at step 430. The acknowledgement received by the control processor at step 340 may be sent by the tuning management processor, such as tuning management processor 210-2 of television receiver 200 of
In response to receiving the acknowledgment at step 430, the control processor may provide a request for recording/reception of an nth television channel of the multiple television channels determined at step 410. The request provided at step 435 may be created by the control processor and sent to the tuning management processor. The request sent at step 435 may be in the same format as the request sent at step 415, but may instead indicate recording of the nth television channel is to commence. This nth television channel of the multiple television channels may be transmitted as part of the same transponder stream as the first television channel. The first time step 435 of method 400 is performed, the nth television channel is the second television channel of the multiple television channels; the second time step 435 is performed, the nth television channel is the third television channel of the multiple television channels, etc.
At step 440, recording of the nth television channel may be configured. Configuring of recording of the nth television channel may be performed by the tuning management processor in response to the request being received at step 435 from the control processor. Configuring recording of the nth television channel by the tuning management processor may involve multiple steps. Such multiple steps are shown in
At step 441, the PIDs for the audio and video of the nth television channel may be determined using the PMT that was previously constructed at step 422. By using the PMT, the tuning management processor can determine the PIDs associated with the nth television channel of the multiple television channels to be recorded. In addition to PIDs for the audio and video of the nth television channel being identified using the PMT at step 441, PIDs for other data related to the nth television channel, such as ECMs related to the nth television channel, may be identified.
At step 442, a PID filter may be created and initialized for the audio and video packets associated with the nth television channel. The PIDs used for the PID filter may be based on the PIDs identified at step 441. Therefore, the PID filter created at step 442 may filter audio, video, and/or other data (e.g., ECMs) related to the nth television channel. The audio, video, and/or other data may begin being recorded for the nth television channel to a file at step 443. Such recording may continue until the command is received by the tuning management processor that indicates recording of the nth television channel is to cease. Following step 443, configuration of recording the first television channel may be considered complete.
Following configuration of the recording of the nth television channel being completed, an acknowledgment may be created and transmitted to the control processor that indicates configuration of recording of the nth television channel has occurred at step 445. The acknowledgement received by the control processor at step 445 may be sent by the tuning management processor, such as tuning management processor 210-2 of television receiver 200 of
At step 450, it may be determined if one or more television channels of the multiple television channels determined at step 410 still need to have recording initialized. If yes, method 400 may return to step 435 and repeat for successive television stations of the plurality of television stations. In some embodiments, four television channels transmitted as part of the same transponder stream are scheduled to begin at the same time. If at step 450 no additional television channels are determined to need to be initialized. Method 400 may the wait until recording of one or more of the television programs is to cease.
At step 455, a command may be issued to the tuning management processor to cease recording one or more of the television channels. The control processor may issue an individual command for each television channel being recorded that indicates recording of the television program is to cease. Each command may indicate the television channel. The control processor may not wait for any acknowledgement when sending cease-recording commands. When the cease-recording commands are received by the tuning management processor, the tuning management processor may cease recording the television channels to their respective files. The cease-recording commands may be based on a time indicated by the timers stored at step 405. In some embodiments, a single command issued by the command processor may cease recording of each of the multiple television channels.
A computer system as illustrated in
The computer system 500 is shown comprising hardware elements that can be electrically coupled via a bus 505 (or may otherwise be in communication, as appropriate). The hardware elements may include one or more processors 510, 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 515, which can include without limitation a mouse, a keyboard, and/or the like; and one or more output devices 520, which can include without limitation a display device, a printer, and/or the like.
The computer system 500 may further include (and/or be in communication with) one or more non-transitory storage devices 525, 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 (“RAM”), and/or a read-only memory (“ROM”), 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 system 500 might also include a communications subsystem 530, 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, etc.), and/or the like. The communications subsystem 530 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 500 will further comprise a working memory 535, which can include a RAM or ROM device, as described above.
The computer system 500 also can comprise software elements, shown as being currently located within the working memory 535, including an operating system 540, device drivers, executable libraries, and/or other code, such as one or more application programs 545, 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. Merely by way of example, one or more procedures described with respect to the method(s) discussed above 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 non-transitory storage device(s) 525 described above. In some cases, the storage medium might be incorporated within a computer system, such as computer system 500. In other embodiments, the storage medium might be separate from a computer system (e.g., a removable medium, such as a compact disc), 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 system 500 and/or might take the form of source and/or installable code, which, upon compilation and/or installation on the computer system 500 (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 system 500) 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 500 in response to processor 510 executing one or more sequences of one or more instructions (which might be incorporated into the operating system 540 and/or other code, such as an application program 545) contained in the working memory 535. Such instructions may be read into the working memory 535 from another computer-readable medium, such as one or more of the non-transitory storage device(s) 525. Merely by way of example, execution of the sequences of instructions contained in the working memory 535 might cause the processor(s) 510 to perform one or more procedures of the methods described herein.
The terms “machine-readable medium” and “computer-readable medium,” as used herein, 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 system 500, various computer-readable media might be involved in providing instructions/code to processor(s) 510 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 include, for example, optical and/or magnetic disks, such as the non-transitory storage device(s) 525. Volatile media include, without limitation, dynamic memory, such as the working memory 535.
Common forms of physical and/or tangible computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punchcards, papertape, any other physical medium with patterns of holes, 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) 510 for execution. Merely 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 500.
The communications subsystem 530 (and/or components thereof) generally will receive signals, and the bus 505 then might carry the signals (and/or the data, instructions, etc. carried by the signals) to the working memory 535, from which the processor(s) 510 retrieves and executes the instructions. The instructions received by the working memory 535 may optionally be stored on a non-transitory storage device 525 either before or after execution by the processor(s) 510.
It should further be understood that the components of computer system 500 can be distributed across a network. For example, some processing may be performed in one location using a first processor while other processing may be performed by another processor remote from the first processor. Other components of computer system 500 may be similarly distributed.
The methods, systems, and devices discussed above are examples. Various configurations may omit, substitute, or add various procedures or 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.
Having described several example configurations, various modifications, alternative constructions, and equivalents may be used without departing from the spirit of the disclosure. For example, the above elements may be components of a larger system, wherein other rules may take precedence over or otherwise modify the application of the invention. Also, a number of steps may be undertaken before, during, or after the above elements are considered. Accordingly, the above description does not bind the scope of the claims.
This application claims priority to U.S. provisional application 61/611,483, filed Mar. 15, 2012, entitled “Reception, Recording, Storage, and Manipulation of Multiple Television Channels”, the entire disclosure of which is hereby incorporated by reference for all 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 | Aug 2002 | A1 |
20020120925 | Logan | Aug 2002 | A1 |
20020126221 | Link | Sep 2002 | A1 |
20020141431 | Tripathy | Oct 2002 | A1 |
20020144259 | Gutta et al. | Oct 2002 | A1 |
20020144266 | Goldman et al. | Oct 2002 | A1 |
20020152299 | Traversat et al. | Oct 2002 | A1 |
20020164147 | Suda | Nov 2002 | A1 |
20020168178 | Rodriguez et al. | Nov 2002 | A1 |
20020174430 | Ellis et al. | Nov 2002 | A1 |
20020184638 | Agnihortri et al. | Dec 2002 | A1 |
20020188943 | Freeman et al. | Dec 2002 | A1 |
20030005454 | Rodriguez et al. | Jan 2003 | A1 |
20030026423 | Unger et al. | Feb 2003 | A1 |
20030078930 | Surcouf et al. | Apr 2003 | A1 |
20030097659 | Goldman | May 2003 | A1 |
20030110514 | West et al. | Jun 2003 | A1 |
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 | 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 | 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 | 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 |
20130243398 | Templeman et al. | Sep 2013 | A1 |
20130243399 | Casagrande et al. | Sep 2013 | A1 |
20130243401 | Casagrande | Sep 2013 | A1 |
20130243402 | Kummer et al. | Sep 2013 | A1 |
20130243403 | Martch | Sep 2013 | A1 |
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 et al. | May 2014 | A1 |
20140201767 | Seiden et al. | Jul 2014 | A1 |
20140341377 | Kummer et al. | Nov 2014 | A1 |
20140344858 | Minnick | Nov 2014 | A1 |
20140363139 | Kirby | Dec 2014 | A1 |
20140376884 | Lovell | Dec 2014 | A1 |
20150040166 | Tamura et al. | Feb 2015 | A1 |
20150095948 | Kummer et al. | Apr 2015 | A1 |
20150104146 | Higuchi et al. | Apr 2015 | A1 |
20150121430 | Templeman | Apr 2015 | A1 |
20150208119 | Casagrande et al. | Jul 2015 | A1 |
20150208125 | Robinson | Jul 2015 | A1 |
20150228305 | Templeman et al. | Aug 2015 | A1 |
20150245089 | Protrebic et al. | 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 |
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 |
1 168 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 |
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 |
2013028829 | Feb 2013 | WO |
2013028835 | Feb 2013 | WO |
2013138606 | Sep 2013 | WO |
2013138608 | Sep 2013 | WO |
2013138610 | Sep 2013 | WO |
2013138638 | Sep 2013 | WO |
2013138689 | Sep 2013 | WO |
2013138740 | Sep 2013 | WO |
2016066443 | May 2016 | WO |
Entry |
---|
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. |
International Search Report and Written Opinion of PCT/US2013/031440 mailed May 30, 2013, 14 pages. |
International Preliminary Report on Patentability for PCT/US2013/031440 mailed Sep. 25, 2014, 8 pages. |
The Office Action dated Nov. 6, 2014 for Mexican Patent Application No. MX/a/2013/014677 is not translated into English, 2 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, 2015, 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/797,173, filed Mar. 12, 2013 Notice of Allowance mailed Nov. 24, 2014, 37 pages. |
U.S. Appl. No. 13/757,168, filed Feb. 1, 2013 Notice of Allowance mailed Oct. 14, 2014, 28 pages. |
U.S. Appl. No. 13/294,005, filed Nov. 11, 2011 Notice of Allowance mailed Oct. 31, 2014, 24 pages. |
U.S. Appl. No. 13/292,047, filed Nov. 8, 2011 Final Office Action mailed Jan. 13, 2015, 22 pages. |
U.S. Appl. No. 13/215,598, filed Aug. 23, 2011 Non-Final Office Action mailed Nov. 25, 2014, 18 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. |
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. |
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. |
Author Unknown, “EE Launches home TV service in UK,” dated Oct. 8, 2014, 3 pages. Retrieved on Oct. 13, 2014 from http://www.bbc.com/news/technology-29535279. |
Author Unknown, “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. |
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/EE-to-launch-TV-set-top-box.html. |
U.S. Appl. No. 13/795,914, filed Mar. 6, 2013, Non-Final Office Action mailed Oct. 11, 2013, 17 pages. |
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 PCT/IB2003/005737 mailed on Mar. 3, 2004. |
Jensen, Craig, “Fragmentation: the condition, the cause, the cure” ′Online!, Executive Software International, 1994; retrieved from Internet: <URL: www.executive.com/fragbook/fragbook.htm> retrieved on Mar. 2, 2004! * Chapter: “How a disk works”, Section: “The original problem”. |
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. |
Jung, J., et al., “Design and Implementation of a Multi-Stream CableCARD with a High-Speed DVB-Common Descrambler,” ACM Multimedia, 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, 2013, 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, 2014, 41 pages. |
U.S. Appl. No. 13/291,014, filed Nov. 7, 2011, 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, 2011, 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/340,190, filed Jul. 24, 2014, Non-Final Rejection mailed Aug. 31, 2015, 74 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. 13/799,604, filed Mar. 13, 2013, Notice of Allowance mailed Jul. 24, 2015, 34 pages. |
U.S. Appl. No. 13/288,002, filed Nov. 2, 2011 Non Final Rejection mailed Jul. 28, 2015, 29 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. 14/043,617, filed Oct. 1, 2013 Final Office Action mailed Jul. 16, 2015, 45 pages. |
Supplementary European Search Report for EP 13761291.7 mailed Jul. 9, 2015, 8 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. |
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/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 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. |
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/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. |
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 Pat. Appln. No. MX/a/2013/014217 is not translated into English, 3 pages. |
U.S. Appl. No. 13/215,598, filed Aug 23, 2011 Final Office Action mailed May 5, 2015, 17 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/095,860, filed Dec. 3, 2013 Notice of Allowance mailed Jul. 13, 2015, 31 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/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. |
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. 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. |
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. 13/801,994, Non Final Office Action mailed Oct. 7, 2015, 55 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. |
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. |
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/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. 7, 2016, 33 pages. |
U.S. Appl. No. 13/801,994, Final Office Action mailed May 4, 2016, 37 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. |
Decision to Grant from the State Intellectual Property Office (SIPO) for CN 201280031434.7, issued May 12, 2016, all pages. |
Notice of Allowance dated Jan. 15, 2016 for Mexican Patent Application No. MX/a/2014/009928, 1 page. |
Notice of Allowance dated Dec. 16, 2015 for Mexican Patent Application No. MX/a/2014/009919, 1 page. |
First Office Action and Search Report from the State Intellectual Property Office (SIPO) for CN 201280031150.8, issued Aug. 3, 2016, 2 pages. |
Second Office Action issued by State Intellectual Property Office for CN 201280028697.2, issued Jul. 8, 2016, 6 pages. |
Number | Date | Country | |
---|---|---|---|
20130243405 A1 | Sep 2013 | US |
Number | Date | Country | |
---|---|---|---|
61611483 | Mar 2012 | US |