Method and system for associating business rules with received content in a content processing system and generating a content list therefrom
Summary by NHIP
Content Rule Association and Encryption
The method associates content with business rules and material identification at a workflow system before encrypting it into two distinct encrypted versions. The system generates separate content lists for different target types and communicates the selected content via satellite or terrestrial networks.
Claim Score by NHIP
Abstract
A system 100 includes a content management system 221 having a material identification and business rules for content including targets and a work flow system 220 in communication with the content management system and receiving the material identification and targets. The work flow system 220 obtains content having an associated business rule identification and associates the content with the material identification. The content management system 221 associates the content with the business rules and generates a content list in response to the business rules. The content management system 221 receives a selection from the content list. The content delivery network 280 communicates content to a user device in response to the selection.

Term
4.7 yearsleft in the term
Expires 22 June 2031, including 1,429 days of term adjustment.
- Priority and filed
- Granted
- Today
- Expires
28 claims: 2 independent, 26 dependent
- 1Broadest claimClaim Score 42, average(NHIP)A method comprising:providing business rules for content including targets at a content management system, said targets including a user device type;providing the targets and a material identification to a work flow system;obtaining content at the work flow system, said content having an associated business rule identification;associating the material identification with the content at the work flow system;associating the content with the business rules based on the business rule identification and the material identification at the content management system;encrypting the content into a first encrypted content based on the target and the business rules;encrypting the content into a second encrypted content based on the target and the business rules;storing the first encrypted content and the second encrypted content in a content repository;generating a content list in response to the business rules at the content management system for a first target different than a second target based on a type of target when a first target type is different than a second target type;selecting a selection from the content list;and communicating content to a user device in response to the selection from the content repository.
- 15A system comprising:a content management system having a material identification and business rules for content including targets;a work flow system in communication with the content management system and receiving the material identification and targets, said work flow system obtaining content having an associated business rule identification and associating the content with the material identification;a content repository;said content management system associating the content with the business rules based on the business rule identification and the material identification, an encryption module encrypting the content into a first encrypted content based on the target and the business rules and encrypting the content into a second encrypted content based on the target and the business rules;said content management system storing the first encrypted content and the second encrypted content in the content repository and generating a content list in response to the business rules for a first target different than a second target based on a type of target when a first target type is different than a second target type;said content management system receiving a selection from the content list;and a content delivery network communicating content to a user device in response to the selection.
Independent claims2
97 paragraphs in 5 sections, as filed
TECHNICAL FIELD
0001The present disclosure relates to a content processing and delivery system and, more specifically, to a system for processing different types of content for different types of user devices.
BACKGROUND
0002The statements in this section merely provide background information related to the present disclosure and may not constitute prior art.
0003Satellite television has become increasingly popular due to the wide variety of content and the quality of content available. A satellite television system typically includes a set top box that is used to receive the satellite signals and decode the satellite signals for use on a television. The set top box typically has a memory associated therewith. The memory may include a digital video recorder or the like as well as the operating code for the set top box.
0004Satellite television systems typically broadcast content to a number of users simultaneously in a system. Satellite television systems also offer subscription or pay-per-view access to broadcast content. Access is provided using signals broadcast over the satellite. Once access is provided the user can access the particular content. The broadcasting of a large selection of channels and pay-per-view programs uses a considerable amount of satellite resources.
0005Content providers are increasingly trying to determine additional ways to provide content to users. Some content may be desired by a small number of customers. In such a case using valuable satellite resources at peak viewing times may not be cost effective. Less popular content may be broadcast by satellite at less popular viewing times, or may be available for downloading on demand via a broadband connection. Such content may be received and stored by a digital video recorder for later viewing.
SUMMARY
0006The present disclosure provides a system that is capable of supporting many types of devices and various types of processing to accommodate the various types of devices.
0007In one aspect of the disclosure, a method includes providing business rules for content including targets, providing targets and a material identification to a work flow system, obtaining content from the work flow system, said content having an associated business rule identification, associating the content with the business rules, associating the target and material identification with the content at the work flow system, generating a content list in response to the business rules, selecting a selection from the content list and communicating content to a user device in response to the selection.
0008In a further aspect of the disclosure, a system includes a content management system having a material identification and business rules for content including targets and a work flow system in communication with the content management system and receiving the material identification and targets. The work flow system obtains content having an associated business rule identification and associates the content with the material identification. The content management system associates the content with the business rules and generates a content list in response to the business rules. The content management system receives a selection from the content list. The content delivery network communicates content to a user device in response to the selection.
0009Further areas of applicability will become apparent from the description provided herein. It should be understood that the description and specific examples are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure.
DRAWINGS
0010The drawings described herein are for illustration purposes only and are not intended to limit the scope of the present disclosure in any way.
0011<figref idref="DRAWINGS">FIG. 1</figref> is a schematic illustration of a communication system according to the disclosure.
0012<figref idref="DRAWINGS">FIG. 2</figref><i>a </i>is a detailed block diagrammatic view of the content processing system of <figref idref="DRAWINGS">FIG. 1</figref>.
0013<figref idref="DRAWINGS">FIG. 2</figref><i>b </i>is a detailed block diagrammatic view of an alternative content processing system of <figref idref="DRAWINGS">FIG. 1</figref> for web based devices.
0014<figref idref="DRAWINGS">FIG. 3</figref> is a detailed block diagrammatic view of the fixed user device of <figref idref="DRAWINGS">FIG. 1</figref>.
0015<figref idref="DRAWINGS">FIGS. 4</figref><i>a </i>and <b>4</b><i>b </i>are representational views of packets formed according to the present disclosure.
0016<figref idref="DRAWINGS">FIG. 5</figref> is a flowchart illustrating a method for publishing and purging content.
0017<figref idref="DRAWINGS">FIG. 6</figref> is a state diagram for publishing and purging content.
0018<figref idref="DRAWINGS">FIG. 7</figref> is a flowchart illustrating a first method for operating the present disclosure.
0019<figref idref="DRAWINGS">FIG. 8</figref> is a flowchart illustrating a second method for operating the present disclosure.
DETAILED DESCRIPTION
0020The following description is merely exemplary in nature and is not intended to limit the present disclosure, application, or uses. For purposes of clarity, the same reference numbers will be used in the drawings to identify similar elements. As used herein, the term module refers to an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality. As used herein, the phrase at least one of A, B, and C should be construed to mean a logical (A or B or C), using a non-exclusive logical OR. It should be understood that steps within a method may be executed in different order without altering the principles of the present disclosure.
0021The following system is described with respect to a satellite system and a broadband system. The broadband distribution system may be implemented in a cable or telephone-type system. An optical fiber may also be used in the broadband system. Wireless distribution may also be used in the broadband distribution system.
0022While the following disclosure is made with respect to example DIRECTV® broadcast services and systems, it should be understood that many other delivery systems are readily applicable to disclosed systems and methods. Such systems include other wireless distribution systems, wired or cable distribution systems, cable television distribution systems, Ultra High Frequency (UHF)/Very High Frequency (VHF) radio frequency systems or other terrestrial broadcast systems (e.g., Multi-channel Multi-point Distribution System (MMDS), Local Multi-point Distribution System (LMDS), etc.), Internet-based distribution systems, cellular distribution systems, power-line broadcast systems, any point-to-point and/or multicast Internet Protocol (IP) delivery network, and fiber optic networks. Further, the different functions collectively allocated among a head end (HE), integrated receiver/decoders (IRDs) and a content delivery network (CDN) as described below can be reallocated as desired without departing from the intended scope of the present patent.
0023Further, while the following disclosure is made with respect to the delivery of video (e.g., television (TV), movies, music videos, etc.), it should be understood that the systems and methods disclosed herein could also be used for delivery of any media content type, for example, audio, music, data files, web pages, etc. Additionally, throughout this disclosure reference is made to data, information, programs, movies, assets, video data, etc., however, it will be readily apparent to persons of ordinary skill in the art that these terms are substantially equivalent in reference to the example systems and/or methods disclosed herein. As used herein, the term title will be used to refer to, for example, a movie itself and not the name of the movie.
0024Referring now to <figref idref="DRAWINGS">FIG. 1</figref>, a communication system <b>100</b> includes a content processing system <b>102</b> that is used as a processing and transmission source, a plurality of content providers, one of which is shown at reference numeral <b>104</b> and a first satellite <b>106</b>. A second satellite <b>108</b> may also be incorporated into the system. The satellites <b>106</b>, <b>108</b> may be used to communicate different types of information or different portions of various contents from the content processing system <b>102</b>. The system <b>100</b> also includes a plurality of fixed user devices <b>110</b> such as integrated receiver/decoders (IRDs). Wireless communications are exchanged between the content processing system <b>102</b> and the fixed user devices <b>110</b> through one or more of the satellites <b>106</b>, <b>108</b>. The wireless communications may take place at any suitable frequency, such as, for example, Ka band and/or Ku-band frequencies.
0025A mobile user device <b>112</b> may also be incorporated into the system. The mobile user device <b>112</b> may include, but is not limited to, a cell phone <b>114</b>, a personal digital assistant <b>116</b>, a portable media player <b>118</b>, a laptop computer <b>120</b>, or a vehicle-based device <b>122</b>. It should be noted that several mobile devices <b>112</b> and several fixed user devices <b>110</b> may be used in the communication system <b>100</b>. The mobile devices <b>112</b> may each have a separate antenna generally represented by antenna <b>124</b>. The mobile devices may be web-based devices using WiFi, WiMax, cellular broadband or wireless broadband systems.
0026In addition to communication via the satellites <b>106</b>, <b>108</b>, various types of information such as security information, encryption-decryption information, content, or content portions may be communicated terrestrially. Various communication means such as a communication network <b>132</b> include, but are not limited to, the public switched telephone network (PSTN), a terrestrial wireless system, a broadband system, stratospheric platform, an optical fiber, or the like may be used to terrestrially communicate with the fixed user device <b>110</b> or the mobile user device <b>112</b>. To illustrate the terrestrial wireless capability an antenna <b>134</b> is illustrated for wireless terrestrial communication to the mobile user device <b>112</b>.
0027Information or content provided to content processing system <b>102</b> from the media source <b>104</b> may be transmitted, for example, via an uplink antenna <b>138</b> to the satellite(s) <b>106</b>, <b>108</b>, one or more of which may be a geosynchronous or geo-stationary satellite, that, in turn, rebroadcast the information over broad geographical areas on the earth that include the user devices <b>110</b>, <b>112</b>. The satellites may have inter-satellite links <b>107</b> that allow the satellites to communicate signals therebetween. Among other things, the example content processing system <b>102</b> of <figref idref="DRAWINGS">FIG. 1</figref> provides program material or content to the user devices <b>110</b>, <b>112</b> and coordinates with the user devices <b>110</b>, <b>112</b> to offer subscribers pay-per-view (PPV) program services and broadband services, including billing and associated decryption of video programs. Non-PPV (e.g. free or subscription) programming may also be received. To receive the information rebroadcast by satellites <b>106</b>, <b>108</b>, each for user device <b>110</b> is communicatively coupled to a receiver or downlink antenna <b>140</b>.
0028Lists of available content may also be communicated by way of the communication network <b>132</b> or the satellites <b>106</b>, <b>108</b>. The lists may also be made available at a web server. The lists and content may be communicated separately through different means or through the same means.
0029Security of assets broadcast via the satellites <b>106</b>, <b>108</b> may be established by applying encryption and decryption to assets or content during content processing and/or during broadcast (i.e., broadcast encryption). For example, an asset can be encrypted based upon a control word (CW) known to the content processing system <b>102</b> and known to the user devices <b>110</b>, <b>112</b> authorized to view and/or playback the asset. In the illustrated example communication system <b>100</b>, for each asset the content processing system <b>102</b> generates a control word packet (CWP) that includes, among other things, a time stamp, authorization requirements and an input value and then determines the control word (CW) for the asset by computing a cryptographic hash of the contents of the CWP. The CWP is also broadcast to the user devices <b>110</b>, <b>112</b> via the satellites <b>106</b>, <b>108</b>. The user devices authorized to view and/or playback the broadcast encrypted asset will be able to correctly determine the CW by computing a cryptographic hash of the contents of the received CWP. If the user device <b>110</b> is not authorized, the IRD <b>110</b> will not be able to determine the correct CW that enables decryption of the received broadcast encrypted asset. The CW may be changed periodically (e.g., every 30 seconds) by generating and broadcasting a new CWP. In an example, a new CWP is generated by updating the timestamp included in each CWP. Alternatively, a CWP could directly convey a CW either in encrypted or unencrypted form. Other examples of coordinated encryption and decryption abound, including for example, public/private key encryption and decryption.
0030Referring now to <figref idref="DRAWINGS">FIG. 2</figref><i>a</i>, the content processing system <b>102</b> of <figref idref="DRAWINGS">FIG. 1</figref> is illustrated in further detail. The content provider <b>104</b> may include various types of content providers, including those that provide content by way of a satellite <b>200</b>, DVD <b>202</b>, via a network as a file in <b>204</b>, by way of tapes and other means. The content provider <b>104</b> may also provide a content description and other metadata <b>208</b> to the system. An input server <b>212</b> may receive the various content and associated metadata and convert the format in a format conversion system <b>214</b>. A house format asset storage server <b>216</b> may be used to store the content asset in a house format. Still image files, trailers, and other information may also be stored in the house format asset storage server. A workflow management system <b>220</b> is used to control the format conversion system <b>214</b> and the server <b>212</b>. Also, the workflow management system <b>220</b> is coupled to the house format asset storage server <b>216</b> and performs ingest control. The house format asset storage server <b>216</b> provides still images to a content management system <b>221</b> and house format file, video and audio files to the video transport processing system <b>223</b>.
0031The VTPS <b>223</b> may encode the packets containing the content. The encoder may encode the data into various transport formats such as DIRECTV® proprietary formats, or industry standard formats. The encoded data is then packetized into a stream of data packets by a packetizer <b>270</b> that also attaches a header to each data packet to facilitate identification of the contents of the data packet such as, for example, a sequence number that identifies each data packet's location within the stream of data packets (i.e., a bitstream). The header also includes a program identifier (PID) (e.g., a service channel identifier (SCID)) that identifies the program to which the data packet belongs.
0032The stream of data packets (i.e., a bitstream) is then broadcast encrypted by, for example, the well-known Advanced Encryption Standard (AES) or the well-known Data Encryption Standard (DES). In an example, only the payload portion of the data packets are encrypted thereby allowing a user device <b>110</b> to filter, route and/or sort received broadcast encrypted data packets without having to first decrypt the encrypted data packets.
0033The content management system <b>221</b> generally controls the overall movement and distribution of contents through the content processing system <b>102</b>.
0034A licensing and contract information <b>222</b> and ads from ad sales <b>224</b> may be provided to the content management system <b>221</b>. That is, licensing information, tier assignments, pricing and availability may be provided to the content management system. Asset information, file names and durations may be exchanged between the content management system <b>221</b> and the workflow management system <b>220</b>. The asset information, such as file names and durations, may be determined at the server <b>212</b> that is coupled to the workflow management system <b>220</b>.
0035The Content Management System (CMS) <b>221</b> in combination with the SPS (<b>230</b>) is used to provide the requested channel, program associated data (PAD), channel information and program information packets (PIPs). The CMS <b>221</b> may schedule content processing for a plurality of received assets based on a desired program lineup to be offered by the communication system <b>100</b>. For example, a live TV program for which a high demand for reruns might be expected could be assigned a high priority for content processing.
0036A schedule PAD server (SPS) <b>230</b> may be coupled to the CMS and is used to generate a broadband video PAD that is communicated to a conditional access system for broadband video <b>232</b>. The conditional access system for broadband video <b>232</b> may be used to generate control words and control word packet in pairs and provide those to the video transport processing system <b>223</b>.
0037In the illustrated example of <figref idref="DRAWINGS">FIG. 2</figref><i>a</i>, users of the user devices <b>110</b> (of <figref idref="DRAWINGS">FIG. 1</figref>) are charged for subscription services and/or asset downloads (e.g., PPV TV) and, thus, the content processing system <b>102</b> includes a billing system <b>234</b> to track and/or bill subscribers for services provided by the system <b>100</b>. For example, the billing system <b>234</b> records that a user has been authorized to download a movie and once the movie has been successfully downloaded the user is billed for the movie. Alternatively, the user may not be billed unless the movie has been viewed.
0038A billing system <b>234</b> receives pricing and availability information from the content management system <b>221</b>. A conditional access system <b>236</b> receives callback information from the communication network <b>132</b>. The conditional access system may be used to generate authorizations, pay-per-view billing data, and callback data from the billing system <b>234</b>. Remote record requests may also be provided from the conditional access transaction system <b>238</b>. A conditional access system BCC <b>240</b> may be used to generate a conditional access packet from the information from the conditional access system <b>236</b>.
0039The billing system <b>234</b> may generate purchase data that is provided to the enterprise integration (EI) block <b>242</b>. The enterprise integration block <b>242</b> may generate remote record requests to the conditional access transaction system <b>238</b>. Remote record requests may be generated through a web interface such as DIRECTV.com® in block <b>244</b>. Various ordering information, such as ordering broadband video, pay-per-view, and various services may be received at the web interface <b>244</b>. Various trailers may also be accessed by the users through the web interface <b>244</b> provided from the house format asset storage server <b>216</b>. Enterprise integration block <b>242</b> may also receive guide information and metadata from the content management system <b>221</b>.
0040Titles, description and various categories from the content management system <b>221</b> may be provided to the advanced program guide system <b>248</b>. The program guide system <b>248</b> may be coupled to a satellite broadcasting system such as a broadcast transport processing system <b>250</b> that broadcasts content to the users through the satellite <b>106</b>, <b>108</b>.
0041The program guide data generated by the program guide system <b>248</b> may include information that is used to generate a display of guide information to the user, wherein the program guide may be a grid guide and informs the user of particular programs that are broadcast on, particular channels at particular times. The program guide may be a list of content available through a communication means. A program guide may also include information that a user device uses to assemble programming for display to a user. For example, the program guide may be used to tune to a channel on which a particular program is offered. The program guide may also contain information for tuning, demodulating, demultiplexing, decrypting, depacketizing, or decoding selected programs.
0042Content files may also be provided from the content management system <b>221</b> to the content distribution system <b>260</b>.
0043Referring back to the video transport processing system <b>223</b>, the video transport processing system <b>223</b> includes a transport packaging system <b>270</b>. The transport processing system <b>270</b> creates pre-packetized unencrypted files. An encryption module <b>272</b> receives the output of the transport processing system and encrypts the packets. Fully packaged and encrypted files may also be stored in the content repository <b>274</b>. Encryption may take place in the data portion of a packet and not the header portion.
0044One or more content delivery networks <b>280</b> may be used to provide content files such as encrypted or unencrypted and packetized files to the communication network <b>132</b> for distribution to the user devices <b>110</b>, <b>112</b>. The content distribution system <b>260</b> may make requests for delivery of the various content files and assets through the communication network <b>132</b>. The content distribution system <b>260</b> also generates satellite requests and broadcasts various content and assets through the broadcast transport processing system <b>250</b>. Some content delivery networks may be dedicated to a certain type of service or communication means. As will be described in <figref idref="DRAWINGS">FIG. 2</figref><i>b</i>, one content delivery network may be dedicated to web service. Others may be dedicated to mobile phone service. Still others may be dedicated to other types of communication.
0045The communication network <b>132</b> may be a web-based system such as the Internet <b>122</b> which is a multiple-point-to-multiple-point communication network. However, persons of ordinary skill in the art will appreciate that point-to-point communications may also be provided through the communication network <b>132</b>. For example, downloads of a particular content file from a content delivery network may be communicated to a particular user device. Such file transfers and/or file transfer protocols are widely recognized as point-to-point communications or point-to-point communication signals and/or create point-to-point communication paths, even if transported via a multi-point-to-multi-point communication network such as the Internet. It will be further recognized that the communication network <b>132</b> may be used to implement any variety of broadcast system where a broadcast transmitter may transmit any variety of data or data packets to any number of or a variety of clients or receivers simultaneously. Moreover, the communication network <b>132</b> may be used to simultaneously provide broadcast and point-to-point communications and/or point-to-point communication signals from a number of broadcast transmitters or content delivery networks <b>280</b>.
0046The content delivery network <b>280</b> may be implemented using a variety of techniques or devices. For instance, a plurality of Linux-based servers with fiber optic connections may be used. Each of the content delivery networks <b>280</b> may include servers that are connected to the Internet or the communication network <b>132</b>. This allows the user devices to download information or content (example, a movie) from the content delivery network <b>280</b>. The content delivery network <b>280</b> may act as a cache for the information provided from the content repository <b>274</b>. A particular user device may be directed to a particular content delivery network <b>280</b> depending on the specific content to be retrieved. An Internet uniform resource locator (URL) may be assigned to a movie or other content. Further, should one of the delivery networks <b>280</b> have heavy traffic, the content delivery network may be changed to provide faster service. In the interest of clarity and ease of understanding, throughout this disclosure reference will be made to delivering, downloading, transferring and/or receiving information, video, data, etc. by way of the content delivery network <b>280</b>. However, persons of ordinary skill in the art will readily appreciate that information is actually delivered, downloaded, transferred, or received by one of the Internet-based servers in or associated with the content delivery network <b>280</b>.
0047It should be appreciated that the content delivery network <b>280</b> may be operated by an external vendor. That is, the operator of the content delivery network <b>280</b> may not be the same as the operator of the remaining portions of the content processing system <b>102</b>. To download files from the content delivery network <b>280</b>, user devices <b>110</b>, <b>112</b> may implement an Internet protocol stack with a defined application layer and possibly a download application provided by a content delivery network provider. In the illustrated example, file transfers are implemented using standard Internet protocols (file transfer protocol FTP), hyper text transfer protocol (HTTP), etc. Each file received by the user device may be checked for completeness and integrity and if a file is not intact, missing, and/or damaged portions of the files may be delivered or downloaded again. Alternatively, the entire file may be purged from the IRD and delivered or downloaded again.
0048The broadcast transport processing system <b>250</b> may provide various functions, including packetizing, multiplexing and modulating, and uplink frequency conversion. RF amplification may also be provided in the broadcast transport processing system <b>250</b>.
0049Wireless delivery via the satellites <b>106</b>, <b>108</b> may simultaneously include both files (e.g., movies, pre-recorded TV shows, games, software updates, asset files, etc.) and/or live content, data, programs and/or information. Wireless delivery via the satellites <b>106</b>, <b>108</b> offers the opportunity to deliver, for example, a number of titles (e.g., movies, pre-recorded TV shows, etc.) to virtually any number of customers with a single broadcast. However, because of the limited channel capacity of the satellites <b>106</b>, <b>108</b>, the number of titles (i.e., assets) that can be provided during a particular time period is restricted.
0050In contrast, Internet-based delivery via the CDN <b>280</b> can support a large number of titles, each of which may have a narrower target audience. Further, Internet-based delivery is point-to-point (e.g., from an Internet-based content server to a user device <b>110</b>, <b>112</b>) thereby allowing each user of the user device <b>110</b>, <b>112</b> to individually select titles. Allocation of a title to satellite and/or Internet-based delivery or content depends upon a target audience size and may be adjusted over time. For instance, a title having high demand (i.e., large initial audience) may initially be broadcast via the satellites <b>106</b>, <b>108</b>, then, over time, the title may be made available for download via the CDN <b>280</b> when the size of the target audience or the demand for the title is smaller. A title may simultaneously be broadcast via the satellites <b>106</b>, <b>108</b> and be made available for download from the CDN <b>280</b> via the communication network <b>132</b>.
0051In the example communication system <b>100</b>, each asset (e.g., program, title, content, game, TV program, etc.) is pre-packetized and, optionally, pre-encrypted and then stored as a data file (i.e., an asset file). Subsequently, the asset file may be broadcast via the satellites <b>106</b>, <b>108</b> and/or sent to the CDN <b>280</b> for download via the CDN <b>280</b> (i.e., Internet-based delivery). In particular, if the data file is broadcast via the satellites <b>106</b>, <b>108</b>, the data file forms at least one payload of a resultant satellite signal. Likewise, if the data file is available for download via the CDN <b>280</b>, the data file forms at least one payload of a resultant Internet signal.
0052It will be readily apparent to persons of ordinary skill in the art that even though at least one payload of a resultant signal includes the data file regardless of broadcast technique (e.g., satellite or Internet), how the file is physically transmitted may differ. In particular, transmission of data via a transmission medium (e.g., satellite, Internet, etc.) comprises operations that are: (a) transmission medium independent and b) transmission medium dependent. For example, transmission protocols (e.g., transmission control protocol/Internet protocol (TCP/IP), user datagram protocol (UDP), encapsulation, etc.) and/or modulation techniques (e.g., quadrature amplitude modulation (QAM), forward error correction (FEC), etc.) used to transmit a file via Internet signals (e.g., over the Internet <b>122</b>) may differ from those used via satellite (e.g., the satellites <b>106</b>, <b>108</b>). In other words, transmission protocols and/or modulation techniques are specific to physical communication paths, that is, they are dependent upon the physical media and/or transmission medium used to communicate the data. However, the content (e.g., a file representing a title) transported by any given transmission protocol and/or modulation is agnostic of the transmission protocol and/or modulation, that is, the content is transmission medium independent.
0053The same pre-packetized and, optionally, pre-encrypted, content data file that is broadcast via satellite may be available for download via Internet, and how the asset is stored, decoded and/or played back by the user devices <b>110</b> is independent of whether the program was received by the user devices <b>110</b> via satellite or Internet. Further, because the example content processing system <b>102</b> of <figref idref="DRAWINGS">FIG. 1</figref> broadcasts a live program and a non-live program (e.g., a movie) by applying the same encoding, packetization, encryption, etc., how a program (live or non-live) is stored, decoded and/or played back by the user devices <b>110</b> is also independent of whether the program is live or not. Thus, user devices <b>110</b>, <b>112</b> may handle the processing of content, programs and/or titles independent of the source(s) and/or type(s) of the content, programs and/or titles. In particular, example delivery configurations and signal processing for the example content delivery system of <figref idref="DRAWINGS">FIG. 2</figref><i>a </i>are discussed in detail below.
0054Referring now to <figref idref="DRAWINGS">FIG. 2</figref><i>b</i>, an alternative content processing system <b>102</b>′ suitable for web-based systems is illustrated. The system in <figref idref="DRAWINGS">FIG. 2</figref><i>b </i>may also be used together with that of <figref idref="DRAWINGS">FIG. 2</figref><i>a </i>so that different methods for distribution can take place. The content processing system <b>102</b>′ shares many components with those of the content processing system <b>102</b>. Therefore, the detail associated with these elements will not be described again. The same reference numerals are used to describe the same elements. This embodiment is different from the embodiment illustrated in <figref idref="DRAWINGS">FIG. 2</figref><i>a </i>in that the content processing system <b>102</b>′ is used for web-based devices. Various devices may be web-based devices and include those illustrated in <figref idref="DRAWINGS">FIG. 1</figref> as reference numerals <b>114</b>-<b>122</b>. The web-based devices may be WiMax, WiFi, or otherwise wireless broadband-capable. Various types of content are provided by the content provider <b>104</b>, are provided to the workflow system <b>220</b> in a similar manner to that illustrated in <figref idref="DRAWINGS">FIG. 2</figref>. In this embodiment, various license information, tier assignments and pricing availability are provided to the content management system <b>221</b> from the licensing/contracts <b>222</b> and ad sales <b>224</b>. Various types of information that are entered into the content management system <b>221</b> may be referred to as business rules. The various business rules may be added manually or may be added automatically based upon various contracts with various contract dividers. The business rules may also include the pricing, the availability, and the type of target such as a set top box, a mobile device or a web device. Also, the availability, such as timing of the content, may be provided. The content management system <b>221</b> provides encoding commands such as the various types of targets, material identifications, and the like. The workflow management system <b>220</b> provides the content management system <b>221</b> collects various asset metadata including the file name, duration of the file, and the like.
0055The content management system <b>221</b> links the business rules with the content.
0056The content management system <b>221</b> provides the enterprise integration module <b>242</b> with billing data such as various pay-per-view numbers, publishing dates, and prices. This information may be provided to an on-demand web services <b>282</b>.
0057The content management system <b>221</b> may also provide a content list or inventory to a web portal <b>284</b>. Account information may be provided to the web portal <b>284</b> from the enterprise integration module <b>242</b>. Inventory metadata may be provided from the web portal to the on-demand web service <b>282</b>. A digital rights management (DRM) license server <b>286</b> may be used to provide content license information to the web portal <b>284</b>. The web portal <b>284</b> may be used to provide inventory metadata to the DRM license server <b>286</b>.
0058A digital rights management server <b>288</b> may receive content licenses from the digital rights management license server <b>286</b>. The content management system <b>221</b> may provide digital rights management parameters to a digital rights management packager <b>290</b>. The digital rights management packager <b>290</b> may provide an encrypted content file to the content repository <b>274</b> for storage therein. The content repository <b>274</b> may also receive encoded content files and posters from the workflow management system <b>220</b>. The file posters and other information may be associated with the various content files when stored within the content repository <b>274</b>. It should be noted that the content files may be encrypted or non-encrypted and may also have the digital rights associated therewith. One suitable example for providing digital rights is using a Windows Media® management-type system.
0059The content management system <b>221</b> provides a distribute command to the content distribution system <b>260</b>. The file location, publication dates, expiration dates, purge dates, and the like may be provided to the content distribution system. The content distribution system communicates upload commands to the content delivery network <b>280</b>. In this embodiment, the content delivery network <b>280</b> may be a web-based network. As will be evident to those skilled in the art, various types of content delivery networks may be used for various types of content. In one aspect of the disclosure, one content delivery network may be provided for each different type of user device. For example, for distributing video to a cellular phone, a cellular phone content delivery network may be used. For a set top box, a set top box content delivery network may be used. Different rights and different encoding schemes may be used for the corresponding different user devices.
0060The content delivery network <b>280</b> provides content to the user devices <b>110</b> or <b>112</b>. The user devices may generate download commands by communicating with the web service <b>282</b>. The web service <b>282</b> may communicate inventory metadata account information that is requested. For example, a content list of available content may be provided to the user devices <b>110</b>/<b>112</b>.
0061The digital rights management server <b>288</b> may provide licenses that are requested by the system. The web portal <b>284</b> may grant pre-delivery licenses to the user device <b>110</b>/<b>112</b>. Download commands from the web service <b>282</b> may be provided to the content delivery network <b>280</b> to initiate download of content from the content delivery network <b>280</b>.
0062The web-based device may obtain the content list from the web portal <b>284</b> so that content available for downloading to the user device may be provided to the user device. Upon selection from the list, a particular piece of content may be provided to the user device. The enterprise integration module <b>242</b> generates a bill in response to the downloading of content from the system. The billing information is coordinated with the information from the content user so that the proper user is billed.
0063Referring now to <figref idref="DRAWINGS">FIG. 3</figref>, the user device <b>110</b> may be one of any variety of devices, for example, a set-top box, a home media server, a home media center (HMC), a personal computer (PC) having a receiver card installed therein, etc. A display device <b>300</b> such as a television set, a computer monitor, a portable media player or the like may be coupled to the user device <b>110</b>. The user device <b>110</b> may be an integrated receiver decoder, a satellite television receiver or the like for displaying and/or playback of received programming.
0064The receive antenna <b>140</b> (<b>124</b> on a mobile device) receives signals conveying a modulated multiplexed bitstream from the satellites <b>106</b>, <b>108</b>. Within the receive antenna <b>140</b>, the signals are coupled from a reflector and feed to a low-noise block (LNB) <b>302</b>, which amplifies and frequency downconverts the received signals. The LNB <b>302</b> output is then provided to a receiver <b>304</b>, which receives, demodulates, depacketizes, demultiplexes, decrypts and decodes the received signal to provide audio and video signals to the display device <b>300</b> or a recorder <b>306</b>, or both. The memory device <b>306</b> may be implemented separately from or within the user device <b>110</b>. The receiver <b>304</b> is responsive to user inputs to, for example, tune to a particular program.
0065To store received and/or recorded programs and/or assets, the memory device <b>306</b> may include any of a variety of storage devices such as a hard disk drive, DVR, or other types of memory devices. The memory device <b>306</b> may be used to store the packetized assets and/or programs received via the satellites <b>106</b>, <b>108</b> and/or the CDN <b>280</b>. In particular, the packets stored on memory device <b>306</b> may be the same encoded and, optionally, encrypted packets created by the content processing system <b>102</b> and transmitted via the satellites <b>106</b>, <b>108</b> and/or made available for download via the CDN <b>280</b>.
0066The memory device <b>306</b> may also be a device capable of recording information on, for instance, analog media such as videotape or computer readable digital media such as a hard disk drive (HDD), a digital versatile disc (DVD), a compact disc (CD) and/or any other suitable media.
0067To communicate with any of a variety of clients, media players, etc., the illustrated example the user device <b>110</b> includes one or more connection interface modules <b>308</b> (e.g., USB, serial port, Firewire, etc.). The connection interface module <b>306</b> may act as a network interface that implements, for example, an Ethernet interface. Should a device be strictly web-based, the LNB <b>140</b> and antenna <b>140</b> may not be used.
0068Each user device <b>110</b> may connect to the communication network such as the Internet <b>122</b> via any of a variety of technologies, for instance, a voice-band and/or integrated services digital network (ISDN) modem connected to a conventional PSTN, a wireless broadband connection (e.g., IEEE 802.11b, 802.11g, etc.), a broadband wired connection (e.g., ADSL, cable modems, etc.), a wired Ethernet connection (e.g., local area network (LAN), wide area network (WAN), etc.), a leased transmission facility (e.g., a digital signal level 1 circuit (a.k.a. a DS1), a fractional-DS1, etc.), etc.
0069The user device <b>110</b> may also include a control module <b>310</b> that is used to control the operation of the various components within the user device.
0070A user interface <b>312</b> may, for example, be a set of push buttons or a remote control interface. The user interface <b>312</b> is used to make selections, input various data, and change the parameters of the user device <b>110</b>. The user interface <b>312</b> may be used together with a graphical user interface displayed on the display device associated with the user device.
0071It should also be noted that the user devices <b>110</b>/<b>112</b> may be configured in a similar manner to those illustrated in <figref idref="DRAWINGS">FIG. 3</figref> through reference number <b>110</b>. Such devices may include an internal antenna rather than an external dish-type antenna that is illustrated in the fixed device as <b>140</b>. Also, external antennas are possible such as a phased array antenna.
0072The recording device <b>306</b> may also be partitioned into a network partition <b>320</b> and a user partition <b>322</b>. Different types of content or assets may be stored in the network partition <b>320</b> or the user partition <b>322</b>. The content stored in the different partitions may relate to the tier of the content. This will be further described below.
0073Referring now to <figref idref="DRAWINGS">FIGS. 4</figref><i>a </i>and <b>4</b><i>b</i>, a packet <b>400</b> having a header <b>402</b> and a data portion <b>404</b> is illustrated. The header <b>402</b> may include a program map table (PMT) <b>406</b>, an SCID/PID portion <b>408</b>, and a cyclic redundancy check portion <b>410</b>. This is representative of the output of the VTPS and the file stored in the content repository. The data portion <b>404</b> may be encrypted or not encrypted, while the header portion <b>402</b> is preferably not encrypted. A signal may be broadcast from the content distribution network with this type of format.
0074In <figref idref="DRAWINGS">FIG. 4</figref><i>b</i>, a second packet <b>420</b> having a reformatted header <b>422</b> and a data portion <b>424</b> is illustrated. The data portion <b>424</b> may be unchanged from data portion <b>404</b>. The reformatted header <b>422</b> includes a second SCID/PID <b>426</b> that has been changed. The header <b>426</b> of the packet <b>420</b> has its identification (SCID/PID) reconfigured so that it may be broadcast by the satellite. Because the SCID/PID is changed, the CRC portion <b>428</b> is also changed to conform to this change.
0075Referring now to <figref idref="DRAWINGS">FIG. 5</figref>, a method of operating the communication system is set forth. In this embodiment, the general method for maintaining the files within the system is set forth. Each content delivery network may have different lifecycle parameters associated therewith. Each content delivery network may act according to the method of <figref idref="DRAWINGS">FIG. 5</figref> using different lifecycle parameters including publication, purge, end times, and the like. In step <b>510</b>, content with metadata is received in the communication system. As mentioned above, the content provider <b>104</b> may provide the content in various forms. In step <b>512</b>, the content is packetized in the VTPS <b>223</b>. Also, as mentioned above, the VTPS may also encrypt the packets or at least the data portions of the packets. In step <b>514</b>, the packets, whether encrypted or not, are stored in the content repository <b>274</b>. In step <b>516</b>, a time for publication is determined. The publication time corresponds to the time that the content is available for download by one of the user devices from the content delivery network <b>280</b>. Various content within the content repository may have different publication times. In step <b>518</b>, the earliest publication time for the various content is determined. In step <b>520</b>, the content file is transferred to the content delivery network <b>280</b> in response to the publication time. That is, the earliest publication time may be used to transfer content to the content delivery network first. The content may be transferred prior to the publication time so that it is available at the publication time. This is in contrast to a typical satellite broadcasting system and to the broadcast TPS system <b>250</b> described in <figref idref="DRAWINGS">FIG. 2</figref>. In a satellite system, the content is broadcast at the air time.
0076In step <b>522</b>, metadata corresponding to the content file is transferred to the content delivery network <b>280</b>. In step <b>524</b>, the metadata may be changed according to information from the content management system. For example, the publication time, the publication end time, and a purge time may be added to the metadata. In step <b>526</b>, the content file is published according to the publication time in the metadata. In step <b>528</b>, the content may be transferred to the user device. In step <b>530</b>, the user device may utilize the content by viewing the content on the display device. In step <b>532</b>, publication is complete at the publication end time. In step <b>534</b>, the content is purged from the content delivery network according to a purge message.
0077Referring now to <figref idref="DRAWINGS">FIG. 6</figref>, a state diagram of the method of <figref idref="DRAWINGS">FIG. 5</figref> is illustrated. The method begins in step <b>600</b> in which the content is placed in the content repository <b>274</b> after possible encryption and packetizing from the VTPS <b>223</b>. In step <b>602</b>, delivery is scheduled by the content management system <b>221</b>. The content distribution system <b>260</b> begins content file transfer to a content delivery network <b>280</b> with metadata in step <b>604</b>. In step <b>606</b>, the content with the metadata is transferred. In step <b>608</b>, the content delivery system completes the content file transfer to the content delivery network <b>280</b>. In step <b>610</b>, the content is fully delivered to the content distribution or delivery network <b>280</b>. In step <b>612</b>, an add operation is received by the content delivery network. An upload status message from the content delivery network (CDN) with a successful status code is provided.
0078In step <b>614</b>, publication is scheduled by setting a publication time. After step <b>614</b>, step <b>616</b> may be performed. In step <b>616</b>, the content delivery network <b>280</b> may receive a publish operation. Also in step <b>616</b>, an upload status message from the content delivery network may be provided to the content distribution system with a successful status code. In step <b>618</b>, the content is published.
0079Referring back to step <b>614</b>, if an update operation message is received and the upload status message from the content delivery network with a successful status code with the published stop time is in the past at <b>620</b>, step <b>622</b> may be performed. Step <b>622</b> ends the publication according to the publication stop time.
0080Referring back to step <b>614</b>, if a receive update operation is received and an upload status message from the content delivery network has a successful status code where the publish start time is in the future in step <b>624</b>, step <b>622</b> completes the publication.
0081Referring back to step <b>618</b>, when the content is published in <b>618</b> and an unpublished operation is received with an upload status message from the content delivery network with a successful status code and a published time in the future, step <b>630</b> is performed which brings the system back to the published scheduled block <b>614</b>.
0082Referring back to step <b>618</b>, if an unpublished operation message is received in step <b>636</b>, and the upload status message from the content delivery network with a successful status code has a publication time in the past, step <b>622</b> is performed which completes the publication. In step <b>618</b>, if a purge operation message is received from the content distribution system and the upload status message from the content distribution network with a successful status code is provided in step <b>638</b>, the content is purged in step <b>640</b>.
0083Referring back to step <b>622</b>, if the publication is complete and a published operation is received with an upload status message from the content delivery network with a successful status code in step <b>644</b>, the content is again published in step <b>618</b>.
0084Referring back to step <b>622</b>, if the publication is complete and a purge operation upload status message is received from the content delivery network with a successful status code in step <b>650</b>, step <b>640</b> purges the content from the system. In step <b>642</b>, the content may be removed from the content repository.
0085Referring back to the publication schedule times block <b>614</b>, if a receive purge operation is received that blocks and an upload status message from the content delivery network has a successful status code, step <b>640</b> is performed in which the content is purged.
0086Referring now to <figref idref="DRAWINGS">FIG. 7</figref>, another method for operating the present disclosure is illustrated. In this example, business rules and content are combined to provide a user selection list and ultimately deliver content to the users. In step <b>710</b>, business rules are determined. The business rules may be determined and entered into the content management system <b>221</b> of <figref idref="DRAWINGS">FIG. 2</figref><i>a </i>or <b>2</b><i>b</i>. The business rules may include various characteristics including the dollar amount, the various targets, such as which user devices are to receive the content, and various other profiles. In step <b>712</b>, the business rules are entered into the content management system and include the targets. The business rules may be entered by an operator in response to various distribution agreements. In step <b>714</b>, the targets are provided to the workflow system. In step <b>716</b>, content that is obtained by the workflow system is provided to the content management system <b>221</b>. The workflow system provides the content with material IDs that are used for further identification once it is received by the content management system. Each content has a material ID associated therewith. In step <b>718</b>, the material ID is associated with the content.
0087In step <b>720</b>, the content and business rule ID is provided to the content management system. In step <b>722</b>, the business rules are associated with the content in the content management system. In step <b>724</b>, the content is encrypted according to the business rules. Encryption may take place at the digital rights management packager in <figref idref="DRAWINGS">FIG. 2</figref><i>b </i>or the encryption module <b>272</b> illustrated in <figref idref="DRAWINGS">FIG. 2</figref><i>a</i>. Encryption may take place according to the business rules. More specifically, the content may be encrypted depending on the end user device or target for which the content is destined. Various types of encryption may be provided to various contents for use in the various systems. That is, when stored in the content repository, several different versions of the content encrypted in different ways may be stored therein. In step <b>726</b>, the encrypted content is stored in the content repository.
0088In step <b>728</b>, a guide or title list is generated. The guide or title list may also be referred to as an inventory list. The inventory or title list is generated in response to the content available in the content repository. Preferably, elements of the list are only provided for content available for the different types of targets or devices. That is, when the content list is received by the various devices, only the content that is available to that device is preferably received. The elements of the list may be compiled by the content management system <b>221</b>. In step <b>730</b>, the guide, title list or inventory is communicated to the user devices. The title list may be provided to the user devices in various ways including through a satellite, through a terrestrial system, through a terrestrial wireless system, through a web-based system, or the like. The content list may be provided in a different way or using a different communication means than the content is provided. For example, a list may be provided through the satellite, whereas the content may be received through a broadband or Internet-based system. Communication to the user devices may also take place on a web-based system. The user devices may be used to obtain information on a website that is in communication with the user device.
0089In step <b>732</b>, a selection is formed at the user device. The selection may be performed by entering or selecting the content from a user interface at the user device. A graphical user interface may have a selection box thereon for selecting. The selection box may be moved using cursors or other devices. Specialized selection buttons or buttons that exist on a system may be used for forming a selection. A signal identifying the selection is formed and communicated to the content processing system. In step <b>734</b>, once a selection is selection, billing information is updated so the proper user device account may be updated. In step <b>736</b>, the content delivery network is selected. The content delivery network may be selected depending on the type of content selected. That is, various content delivery networks may be provided in a particular system. However, only one of the content delivery networks may be used for delivering content to that particular user device based upon the formatting and the like.
0090In step <b>740</b>, the content is played back or stored in the user device. It should be noted that the playback may be performed while recording the content.
0091Referring now to <figref idref="DRAWINGS">FIG. 8</figref>, a specific method for operating the content management system is illustrated. Steps <b>710</b>-<b>722</b> of <figref idref="DRAWINGS">FIG. 7</figref> are shared in this embodiment. In step <b>810</b>, the content type is determined. The content type is based upon the target described above. The target corresponds to the various types of user devices. In this example, a web-based and non-web-based-type system is employed. However, the same decision blocks may be used for various other types of target devices. It should also be noted that more than two different types of targets may be provided. However, in such a system, the same types of logic may be used. In step <b>820</b>, the system determines whether or not the content is destined for a web-based system. In step <b>822</b>, if content is for a web-based system, the block diagram of <figref idref="DRAWINGS">FIG. 2</figref><i>b </i>may be utilized. In step <b>824</b>, digital rights management (DRM) may be applied. Digital rights management may be windows media-based digital rights management or various other types of digital rights management. The digital rights management may also include various types of encryption. In step <b>826</b>, the content with the applied digital rights management and/or encryption is stored in the content repository. In step <b>828</b>, a list is provided for the content available at a web portal. After step <b>828</b>, steps <b>832</b>-<b>740</b> of <figref idref="DRAWINGS">FIG. 7</figref> may be performed.
0092Referring back to step <b>820</b>, if the system is not a web-based system, step <b>830</b> may be performed. In step <b>830</b>, the schematic of <figref idref="DRAWINGS">FIG. 2</figref><i>a </i>may be used to process the content. In step <b>832</b>, encryption is applied to the content based on the target type.
0093In step <b>834</b>, the content, with the applied encryption, is stored in the content repository. In step <b>836</b>, a content list is generated for the particular target. In step <b>838</b>, the content list may be communicated through the program guide or other means. For a satellite-based system, the program guide may be communicated through the satellite. The content list available from the content delivery network may be periodically updated and communicated through the satellite.
0094After step <b>838</b>, steps <b>732</b>-<b>740</b> of <figref idref="DRAWINGS">FIG. 7</figref> may be performed.
0095When the content is provided to the various content delivery networks, various life cycles, purge times, and the like may be associated with the content. The content may have different life cycles, purge times, and other characteristics when provided to each content delivery network. It should also be noted that the same content may be provided through different content delivery networks with different timing characteristics. The different content delivery network may have the same or different types of encryption as well. The various purge times and other life-cycle components are provided in the metadata as described above.
0096The example in <figref idref="DRAWINGS">FIG. 8</figref> is provided for web and non-web-based system. The examples may easily be extended to other types and numbers of systems and targets.
0097Those skilled in the art can now appreciate from the foregoing description that the broad teachings of the disclosure can be implemented in a variety of forms. Therefore, while this disclosure includes particular examples, the true scope of the disclosure should not be so limited since other modifications will become apparent to the skilled practitioner upon a study of the drawings, the specification and the following claims.
Contents5
11 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| WO0169868A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| EP1202507A1 | Cites | European Patent Office (EPO) | Applicant |
| US2001004769A1 | Cites | United States of America | Applicant |
| US2002007491A1 | Cites | United States of America | Applicant |
| US2002009283A1 | Cites | United States of America | Applicant |
| US2002023268A1 | Cites | United States of America | Applicant |
| US2002052969A1 | Cites | United States of America | Applicant |
| US2002059621A1 | Cites | United States of America | Applicant |
| US2002064189A1 | Cites | United States of America | Applicant |
| US2002067745A1 | Cites | United States of America | Applicant |
| US2002103920A1 | Cites | United States of America | Applicant |
| US2002174439A1 | Cites | United States of America | Applicant |
| US2002184642A1 | Cites | United States of America | Applicant |
| US2002184649A1 | Cites | United States of America | Applicant |
| US2003009765A1 | Cites | United States of America | Applicant |
| US2003028889A1 | Cites | United States of America | Applicant |
| US2003063607A1 | Cites | United States of America | Applicant |
| US2003066085A1 | Cites | United States of America | Applicant |
| US2003093806A1 | Cites | United States of America | Applicant |
| US2003121047A1 | Cites | United States of America | Applicant |
| US2004019900A1 | Cites | United States of America | Search report |
| US2004103120A1 | Cites | United States of America | Applicant |
| US2004117839A1 | Cites | United States of America | Applicant |
| US2004120349A1 | Cites | United States of America | Applicant |
| US2004133907A1 | Cites | United States of America | Applicant |
| US2004236620A1 | Cites | United States of America | Applicant |
| US2005013262A1 | Cites | United States of America | Applicant |
| US2005203927A1 | Cites | United States of America | Applicant |
| US2005216952A1 | Cites | United States of America | Applicant |
| US2005265547A1 | Cites | United States of America | Applicant |
| US2006037037A1 | Cites | United States of America | Applicant |
| US2006053347A1 | Cites | United States of America | Applicant |
| US2006143654A1 | Cites | United States of America | Applicant |
| US2006153104A1 | Cites | United States of America | Applicant |
| US2006171390A1 | Cites | United States of America | Applicant |
| US2006206912A1 | Cites | United States of America | Applicant |
| US2006209709A1 | Cites | United States of America | Applicant |
| US2006212900A1 | Cites | United States of America | Applicant |
| US2006212904A1 | Cites | United States of America | Applicant |
| US2006291803A1 | Cites | United States of America | Applicant |
| US2007011709A1 | Cites | United States of America | Applicant |
| US2007022214A1 | Cites | United States of America | Applicant |
| US2007033531A1 | Cites | United States of America | Applicant |
| US2007079168A1 | Cites | United States of America | Applicant |
| US2007089151A1 | Cites | United States of America | Applicant |
| US2007107012A1 | Cites | United States of America | Applicant |
| US2007107032A1 | Cites | United States of America | Applicant |
| US2007113246A1 | Cites | United States of America | Applicant |
| US2007130235A1 | Cites | United States of America | Applicant |
| US2007150922A1 | Cites | United States of America | Applicant |
| US2007199022A1 | Cites | United States of America | Applicant |
| US2007199037A1 | Cites | United States of America | Applicant |
| US2007250487A1 | Cites | United States of America | Applicant |
| US2007283449A1 | Cites | United States of America | Applicant |
| US2007912805A1 | Cites | United States of America | Applicant |
| US2008022347A1 | Cites | United States of America | Applicant |
| US2008137847A1 | Cites | United States of America | Applicant |
| US2008141303A1 | Cites | United States of America | Applicant |
| US2008155613A1 | Cites | United States of America | Applicant |
| US2008216111A1 | Cites | United States of America | Applicant |
| US2008222678A1 | Cites | United States of America | Applicant |
| US2008226073A1 | Cites | United States of America | Applicant |
| US2008282190A1 | Cites | United States of America | Applicant |
| US2008309647A1 | Cites | United States of America | Applicant |
| US2009029644A1 | Cites | United States of America | Applicant |
| US2009031370A1 | Cites | United States of America | Applicant |
| US2009240735A1 | Cites | United States of America | Applicant |
| US2010088497A1 | Cites | United States of America | Applicant |
| US2010189254A1 | Cites | United States of America | Applicant |
| US2010241476A1 | Cites | United States of America | Applicant |
| US5579055A | Cites | United States of America | Applicant |
| US5594490A | Cites | United States of America | Applicant |
| US5852721A | Cites | United States of America | Applicant |
| US6028639A | Cites | United States of America | Applicant |
| US6401243B1 | Cites | United States of America | Applicant |
| US6557171B1 | Cites | United States of America | Applicant |
| US6584083B1 | Cites | United States of America | Applicant |
| US6700932B2 | Cites | United States of America | Applicant |
| US6772209B1 | Cites | United States of America | Applicant |
| US6774926B1 | Cites | United States of America | Applicant |
| US6963590B1 | Cites | United States of America | Applicant |
| US7103906B1 | Cites | United States of America | Search report |
| US7165050B2 | Cites | United States of America | Applicant |
| US7181010B2 | Cites | United States of America | Applicant |
| US7197088B1 | Cites | United States of America | Applicant |
| US7254622B2 | Cites | United States of America | Applicant |
| US7277870B2 | Cites | United States of America | Search report |
| US7301944B1 | Cites | United States of America | Applicant |
| US7394779B2 | Cites | United States of America | Applicant |
| US7496092B2 | Cites | United States of America | Applicant |
| US7646768B2 | Cites | United States of America | Applicant |
| US7778875B2 | Cites | United States of America | Search report |
| US7873072B2 | Cites | United States of America | Applicant |
| US20010004769A1 | Cites | United States of America | Applicant |
| US20020007491A1 | Cites | United States of America | Applicant |
| US20020009283A1 | Cites | United States of America | Applicant |
| US20020023268A1 | Cites | United States of America | Applicant |
| US20020052969A1 | Cites | United States of America | Applicant |
| US20020059621A1 | Cites | United States of America | Applicant |
| US20020064189A1 | Cites | United States of America | Applicant |
2 members in 1 office
Members2
| Document | Office | Kind | |
|---|---|---|---|
| US2009030764A1 | United States of America | A1 | |
| US9104987B2This record | United States of America | B2 |
170 transactions on the USPTO file
Allowed after 1 non-final rejection, 1 final rejection, 1 RCE and 1 appeal.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 1
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Response to 312 Amendment (PTO-271)MN271 | MN271 | |
| Response to Amendment under Rule 312N271 | N271 | |
| Amendment after Notice of Allowance (Rule 312)AllowedA.NA | A.NA | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Mail-Petition Decision - DismissedMPTDI | MPTDI | |
| Petition Decision - DismissedPTDI | PTDI | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Mail PUB other miscellaneous communication to applicantMM327-D | MM327-D | |
| PUB Other miscellaneous communication to applicantM327-D | M327-D | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Petition EnteredPET. | PET. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Reasons for AllowanceEX.R | EX.R | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail BPAI Decision on Appeal - AffirmedMAPDA | MAPDA | |
| BPAI Decision - Examiner AffirmedAPDA | APDA | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Docketing Notice Mailed to AppellantAP_DK_M | AP_DK_M | |
| Assignment of Appeal NumberAPAS | APAS | |
| Appeal Awaiting BPAI DocketingAPWD | APWD | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Appeal ready for BPAI docketingTCWD | TCWD | |
| Reply Brief FiledAPRB | APRB | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Return of Undocketed appeal to the TCTCRD | TCRD | |
| Exam. Ans. Review CompletePACC | PACC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Examiner's AnswerMAPEA | MAPEA | |
| Examiner's Answer to Appeal BriefAPEA | APEA | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Appeal Brief Review CompleteAPBR | APBR | |
| Paralegal or electronic terminal disclaimer approvedP574 | P574 | |
| Terminal Disclaimer FiledDIST | DIST | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Appeal Brief FiledAP.B | AP.B | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Notice of Appeal FiledN/AP | N/AP | |
| Paralegal TD Not acceptedP575 | P575 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Reference capture on IDSRCAP | RCAP |
9 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 9104987
- Application
- 11782563
Titles
- English
- Method and system for associating business rules with received content in a content processing system and generating a content list therefrom
Patent term adjustment
- A delay
- +817 daysthe office missed an examination deadline
- B delay
- +904 dayspendency past three years
- Overlap
- −149 daysdelays counted once
- Applicant delay
- −143 days
- Net adjustment
- 1,429 days
Classification
- CPC, 5
- G06Q10/06
- G06Q10/06316
- H04N21/431
- H04N21/4622
- H04N21/482
- IPC, 7
- H04N5 445
- G06Q10 06
- G06Q30 00
- H04N7 173
- H04N21 431
- H04N21 462
- H04N21 482