Delivering Individualized Content Over a Broadcast Network
Claim Score by NHIP
Abstract
In various embodiments, a unidirectional broadcast network is utilized to provide digital content to users in a manner that allows users' computing devices to maintain synchrony with personal, relevant information. In at least some embodiments, the broadcast network utilizes a data channel and a signaling channel. The data channel is used for broadcasting data to various users, while the signaling channel—typically used for transmitting device or machine specific data—is used to transmit user-specific information associated with the information or data that the user finds relevant. This user-specific information can then be used by the user's mobile computing device to manage, e.g. record and place into device database for time shifted retrieval, such information or digital objects delivered over the broadcast data channel.

Term
2.7 yearsto projected expiry
Projected expiry 9 June 2029, counted from filing; an application has no term until it is granted.
- Priority and filed
- Published
- Today
- Projected expiry
20 claims: 3 independent, 17 dependent
- 1A computer-implemented method comprising:using a signaling channel associated with a broadcast network to transmit user-specific information to a computing device, wherein the user-specific information is configured to be used by the computing device to take an action pertaining to one or more digital objects when the digital objects are broadcast or rebroadcast by the broadcast network;and using a data channel associated with the broadcast network to broadcast one or more digital objects, wherein broadcast of said one or more digital objects is determined by digital objects in which multiple users have expressed a common interest.
- 12Broadest claimClaim Score 75, broad(NHIP)A computer-implemented method comprising:receiving, via a mobile computing device, synchronization information that can be used to synchronize a user's digital object collection on the mobile computing device with a remote library, wherein said synchronization information is received via a signaling channel different from a data channel that transmits digital objects;and using the synchronization information to capture digital objects when the digital objects are broadcast by a broadcast network.
- 18A mobile computing device comprising:one or more processors;one or more computer-readable media;computer-readable instructions on the one or more computer-readable media which, when executed by the one or more processors, cause the one or more processors to implement a method comprising: receiving synchronization information that can be used to synchronize a user's digital object collection on the mobile computing device with a remote library, wherein said synchronization information is received via a signaling channel different from a data channel that transmits digital objects;and using the synchronization information to capture digital objects when the digital objects are broadcast by a broadcast network.
Independent claims3
61 paragraphs in 5 sections, as filed
BACKGROUND
0001As communications networks evolve and become more sophisticated, users are able to manage and access information of interest to them in novel ways. For example, a third party service provider may offer up subscriptions through which users can subscribe and receive digital objects for consumption. Such digital objects can include such things as digital music, video, news, documents and the like.
0002Many users today, however, find themselves on the move with their mobile computing devices. Such mobile scenarios pose challenges for (1) keeping a user's device synchronized with remote data that the user finds interesting or (2) otherwise enabling a user to access and consume information that is interesting to them. For example, leveraging today's uplink/downlink cellular network can provide effective global connectivity coverage, but due to electromagnetic spectrum constraints that limit data throughput, these networks are unlikely to provide a scalable solution for maintaining device synchrony for all users.
SUMMARY
0003In various embodiments, a “Broadcast network”, i.e. a unidirectional “one to many network” is utilized to provide digital content, also termed “digital objects”, to users. In at least some embodiments, this is done in a manner that allows users' computing devices to maintain synchrony with information that is personally relevant to them. In at least some embodiments, the broadcast network utilizes a data channel and a signaling channel. The data channel is used for broadcasting data to all receiver units, while the signaling channel—typically used for transmitting device or machine specific data—is used to transmit user-specific information associated with the information or data that the user finds relevant.
0004In at least some embodiments, the user can specify to the broadcast service provider through some other “back-channel” network link, e.g. home internet, what information or content he/she deems relevant to synchronize on their mobile device. If a signaling channel is available, the signaling channel can then signal to the device when and where the content can be retrieved. This user-specific information can ten be used by the user's mobile computing device to manage, e.g. to record into a local database for time-shifted consumption, such information when the digital objects are broadcast by the broadcast network.
BRIEF DESCRIPTION OF THE DRAWINGS
0005<figref idref="DRAWINGS">FIG. 1</figref> illustrates an exemplary system in accordance with one embodiment.
0006<figref idref="DRAWINGS">FIG. 2</figref> illustrates, on a very small scale, the notion of overlapping interests between users.
0007<figref idref="DRAWINGS">FIG. 3</figref> is a flow diagram that describes steps in a method in accordance with one embodiment.
0008<figref idref="DRAWINGS">FIG. 4</figref> illustrates an exemplary mobile computing device in accordance with one embodiment.
DETAILED DESCRIPTION
0009Overview
0010In various embodiments, a broadcast network is utilized to provide digital content, also termed “digital objects” to users in a manner that allows users' computing devices to maintain synchrony with personally relevant information. The synchronization efforts can, for example, enable a user to maintain synchrony between one or more personal computing devices and a remote library that describes or references that user's relevant information. In at least some embodiments, the broadcast network utilizes a data channel and a signaling channel.
0011The data channel is used for broadcasting data to all receiver units, while the signaling channel—typically used for transmitting device or machine specific data such as supplying the content decryption keys for protected media content or hardware/firmware updates—is used to transmit user-specific information associated with the information or data that the user finds personally relevant. This user-specific information can then be used by the user's computing device, such as a mobile computing device, to take an action relative to one or more digital objects, such as record such digital objects when the digital objects are broadcast by the broadcast network, generate alerts or take other actions as appropriate for a given digital object.
0012The digital objects that are the subject of the synchronization efforts can comprise any suitable type of digital object that users may find personally relevant. Such digital objects can include, by way of example and not limitation, digital music, video, pictures, documents, blogs, sporting event alerts, news items and the like. In the examples that are used throughout this document, digital objects in the form of digital music (files or streams) are used. It is to be appreciated and understood that such exemplary digital objects are not intended to limit application of the claimed subject matter to these objects. Rather, other objects (such as those mentioned above and others) can be utilized without departing from the spirit and scope of the claimed subject matter.
0013Exemplary System Overview
0014<figref idref="DRAWINGS">FIG. 1</figref> illustrates an exemplary system in accordance with one embodiment generally at <b>100</b>. System <b>100</b> includes, in this example, a service provider <b>102</b> that maintains a store <b>104</b> that includes various user information. In this particular example, service provider <b>102</b> might offer up subscriptions for various users and maintain subscription information in the store <b>104</b>. The subscription information can be maintained in a library and can include user information such as user names, billing information and a list of digital objects of interest to the users. Such digital objects might include, for example, a list of objects such as songs to which the user has subscribed or one's latest email.
0015In addition, system <b>100</b> includes a plurality of computing devices shown generally at <b>106</b>. These computing devices can be considered as generally, though not exclusively, non-mobile devices. For example, these devices might be desktop computing devices that generally stay in one location or, alternately, mobile devices such as the ones shown generally at <b>110</b>. These devices are communicatively linked with service provider <b>102</b> via a suitable network such as the Internet.
0016In addition, system <b>100</b> includes a broadcast network <b>108</b> that is configured to (unidirectionally) broadcast content to many users or subscribers. Any suitable broadcast network can be utilized. In at least some embodiments, there is no back-channel communications from the device to the service provider or broadcast network operator. In the absence of a back channel whereby confirmation of delivery can be sent to the network provider, the network provider typically repeats delivery to increase the likelihood of receipt by the user device which often is battery powered and turned-off when not in use. In the worst case of a complete mismatch in time of device activation and broadcast delivery of the digital object, the device itself knows via the signaling channel that a specific media object has not been delivered within a specific time window and can inform the user to seek alternative means of securing this download or to leave his device on at certain time.
0017Optionally, a cellular network <b>109</b> can be provided that includes an optional back channel through which a user can communicate with the broadcast network. One benefit of this configuration is delivery confirmation which the network provider can use to improve its delivery scheduling efficiency.
0018One example of a broadcast network is a so-called conditional access network in which the user is conditionally granted access to the network responsive to some type of agreement with the network provider (which can be service provider <b>102</b> or some other entity). Such an agreement might take the form of a subscription. Contemporary examples of conditional access networks include, by way of example and not limitation, Direct-TV, XM radio, Sirius radio, upcoming DVB-H networks and the like.
0019System <b>100</b> also includes multiple different mobile computing devices—here shown generally at <b>110</b>. In this example, the mobile computing devices include, by way of example and not limitation, cell phones, personal digital assistants and laptop computing devices to name just a few. Other computing devices including those not designed for mobility can be utilized without departing from the spirit and scope of the claimed subject matter.
0020In practice, service provider <b>102</b> can offer up subscriptions or otherwise make it possible for various users to acquire rights in digital objects. For example, in the case where the digital objects comprise digital music, the service provider can allow users to register and pay for downloading various songs. This can be done via one of the computing devices shown generally at <b>106</b>. As noted above, the service provider then maintains a library of information that includes the objects to which the user has subscribed.
0021In practice, the broadcast network operator is often the same entity as the service provider operator.
0022To maintain synchrony between a user's mobile computing device and the library maintained by the service provider, the broadcast network broadcasts, to the computing devices, information that enables the computing devices to receive or otherwise record, alert, or playback a digital object as appropriately designated by the digital object when it is broadcast by the broadcast network <b>108</b>. This information is conveyed, in this embodiment, using a signaling channel associated with the broadcast network. Specifically, in this embodiment, data (such as the digital objects) are broadcast using a data channel. Other information, such as the transmission of content decryption keys, updates, rights, time expiration, delivery window, and other user-specific information that includes digital object synchronization information, is broadcast using the signaling channel. Specific examples of the types of synchronization information and how each can be used are provided below in a section entitled “Implementation Example”.
0023Implementation Example
0024Consider now one particular implementation of the above-described system. <figref idref="DRAWINGS">FIG. 2</figref> illustrates, on a very small scale, the notion of overlapping interests between users.
0025Specifically, consider that there are three users who have subscribed, through the service provider, to receive digital objects. The collection of each user's digital objects is graphically represented by an individual circle. Thus, user 1's digital object collection is represented by the indicated circle, and so on. Notice in this example that, as amongst users, there is some overlap in their interest (indicated by the hatched area). Specifically, the collection of users has digital objects in which they are commonly interested. In the scenario in which the digital objects comprise music, the music that falls into the overlapping region might be the most popular songs at the time for a particular class of users.
0026In this particular example, the service provider or broadcast network can base their delivery schedule of particular digital objects based on a “majority rule” policy among its users. The more demanded a particular object, the higher priority for broadcast and rebroadcast. With a statistically based delivery methodology, the broadcaster of the objects can utilize the signaling channel to notify individual user mobile computing devices when digital objects relevant to the user are going to be broadcast. Once the mobile computing device understands when a particular digital object is going to be broadcast (and rebroadcast), it can arrange to record the digital object for its user.
0027In this manner, a user's collection of digital objects on their mobile computing device can be kept synchronized with a library that reflects the objects in which the user is interested.
0028Consider now one example of synchronization and what types of synchronization information can be sent using the exemplary signaling channel. In at least some embodiments, synchronization pertains to or is influenced by different activities that can occur on the mobile computing device, and/or activities that are determined by the service provider. Responsive to these different types of activities, different types of information can be sent.
0029A first activity is an add activity in which a digital object is added to the mobile computing device. This can occur at a couple of different times. The first time that an object can be added is when the device is initially synchronized. The second time that an object can be added is when a user has added a digital object that is not currently present to their collection. In the add scenario, the broadcast network uses the signaling channel to send synchronization information to the device that indicates when to record a particular digital object. In at least some embodiments this synchronization information includes a start recording time, a record duration time, an “activity” tag (e.g. pertaining to an add, delete, notify, etc. activity), rebroadcast times, and a broadcast channel or frequency number. Optionally, a content ID of the digital object can be sent in the signaling channel as well. This optional information can be useful in notifying the user of non-delivery of a specific content item during its rebroadcast schedule. In at least some embodiments, the content ID is sent in the data channel when the digital object is broadcast. Thus, by knowing when to start and stop recording on a particular channel, the mobile computing device can capture the digital object when it is broadcast.
0030A second activity is a delete activity in which a user or the service provider deletes the digital object. This can occur when, for example, a user pares their library or their rights have expired. In this instance, the synchronization data includes the content ID of the digital object being deleted.
0031A third activity is a null or not sent activity in which the particular digital object of interest to the user is not scheduled for broadcast. This informs the user that they must obtain the object by other means. In this case, the content ID of the digital object that is the subject of the null activity can be sent. In this case, the user would have to find alternative means to include the object on their mobile computing device.
0032In at least some embodiments, the signaling channel can be used to send the actual digital objects to individual users. For example, consider the case in which a user has a digital object in their library that is an obscure song that is not likely to be requested frequently. In this case, the signaling channel can be used to send the actual digital object to the user's mobile computing device.
0033It is to be appreciated and understood that any suitable signaling channel can be used to implement the above-described methodology. Characteristics or properties of such signaling channels can include, by way of example and not limitation, that the channel is typically used to send machine-specific or machine-associated data. Additionally, at least some of such channels are typically not a primary data channel that sends data for consumption by individual users. Rather, the data that is sent is typically consumed by the individual device—such as content protection keys or updates.
0034One specific non-limiting example of a signaling channel is that which can be used to send so-called Entitlement Management Messages (EMMs) to address individual devices with messages, commands and service keys. EMMs do not typically have to be transmitted in a synchronous manner with a media payload, but rather are transmitted in advance in order to give access to an authorized subscriber. To be sure that an EMM is received by the user to renew a subscription, the message is typically repeated sufficiently often. EMMs are therefore organized in cycles for broadcasting.
0035Exemplary Method
0036<figref idref="DRAWINGS">FIG. 3</figref> is a flow diagram that describes steps in a method in accordance with one embodiment. The method can be implemented in connection with any suitable hardware, software, firmware or combination thereof. In at least some embodiments, the method is implemented in software. In addition, in the depicted flow diagram, various acts or steps are shown as being performed by different entities such as, for example, a web service/application, a service provider, a broadcaster or broadcast network (which may or may not be the service provider), and a mobile device.
0037Step <b>300</b> notifies a service provider to download specific content to a specific device. This step can be accomplished by a user via a suitable web service or application or, in certain circumstances, e.g. sport news alerts, can be accomplished by the service provider itself. In at least some embodiments the content resides in the form of one or more digital objects such as those mentioned above. This step can be performed when, for example, a user initially acquires rights in a digital object.
0038Step <b>302</b> ascertains whether there are any update requests. This step can be accomplished by a suitably configured service provider responsive to input that indicates that there is an update request. In at least some embodiments, update requests can be generated as a result of different entities. For example, the user may acquire rights in and consequently receive one or more new or additional digital objects on their non-mobile computing device. In this case, an update message would be created and sent to a broadcaster (step <b>304</b>). Alternately or additionally, the user's rights in a particular digital object may expire or otherwise change. In this case, an update message would be created and sent to the broadcaster (step <b>304</b>).
0039If, on the other hand, an update request is not received, step <b>306</b> ascertains whether there are any pending periodic updates. If not, the method loops back to step <b>302</b>. If there are pending periodic updates, the method branches to step <b>304</b> to create and send an update message to the broadcaster.
0040Step <b>308</b> receives and translates the update request into a message that can be sent to mobile devices via a signaling channel. In the illustrated and described embodiment, this message is an EMM message. It is to be appreciated and understood that other messages using other signaling channels can be used without departing from the spirit and scope of the claimed subject matter. In the illustrated example this step is performed by a broadcaster. The broadcaster may or may not be the same entity as the service provider. It is to be appreciated and understood that in the absence of a signaling channel on the broadcast network, the method would skip to step <b>322</b> whereby the mobile device has been user programmed to capture predetermined content.
0041Step <b>310</b> ascertains whether all of the requests have been translated into a valid EMM. If not, step <b>312</b> creates an error message EMM. If all (or any) of the requests have been translated into valid EMMs, step <b>314</b> sends periodic EMMs to the addressable mobile computing device. In at least some embodiments, delivery is based on the collective statistics of demand by the overall user base of the network operator. Additionally, to assure receipt, delivery of the digital object over the data channel and the EMM over the signaling channel will be frequently rebroadcast.
0042Step <b>316</b> receives and processes the EMM. This step is performed by the mobile computing device. Here, the mobile computing device receives the EMM via the signaling channel. Step <b>318</b> determines whether there are any error messages in the EMM. If there are, step <b>320</b> displays the error message for the subscriber or user. If the EMM contains no error messages and/or there is content described in the EMM, step <b>322</b> captures the content—here, the digital objects—according to the instructions contained in the EMM. Recall from the discussion above that the message that is received that enables the content to be captured can contain synchronization information such as a start and stop recording time, subsequent rebroadcast time, as well as a channel number corresponding to the channel over which the digital object is to be broadcast. Additionally, the EMM <b>1</b> itself could contain the digital object. In such case, the mobile device extracts the message data from the digital object.
0043By using a signaling channel, such as an EMM channel, an out of band mechanism is provided, independent of a data channel, that can be used to synchronize a user's mobile computing device such that their computing device remains up-to-date with a library that references particular digital objects in which the user has an interest.
0044Exemplary Mobile Computing Device
0045<figref idref="DRAWINGS">FIG. 4</figref> illustrates an exemplary mobile computing device that can be used to implement one or more of the embodiments described above, generally at <b>400</b>. In this particular example, mobile computing device <b>400</b> includes one or more processors <b>402</b> and one or more computer-readable media <b>404</b>. Here, the computer-readable media includes computer-readable instructions in the form of software that is executable by processor(s) <b>402</b> to implement the functionality described above. Specifically, in this example, computer-readable media includes a synchronization module <b>406</b> that is programmed to implement the functionality described above. In addition, the computer-readable media includes an object store <b>408</b> in which various digital objects can be stored. In addition, device <b>400</b> includes a rendering engine module <b>407</b> that is configured to render the digital objects. All user components, in this example, are orchestrated by an application module <b>409</b>, which also is responsible for compliance with the rights and restrictions associated with the digital object.
0046Further, device <b>400</b> includes a receiver module <b>410</b> that is configured to receive transmissions over both data and signaling channels. In this case, the transmissions that are received over the signaling channel can include synchronization information such as that described above.
0047In at least some embodiments, as noted above, the digital objects can take the form of digital music. Having now described some basic principles of operation, consider now an exemplary use scenario.
0048Exemplary Use Scenario
0049Consider that Bob wishes to synchronize his in-dash satellite radio unit with his Internet music subscription service. In this case, by leveraging his satellite radio's conditional access signaling channel, the music that Bob has purchased or subscribed to through this service can be automatically downloaded to his car head end unit as described above. As a result, Bob can now access all of his music. The same methodology can also be applied to Bob's email, pictures, address book, word documents and the like.
0050Payment Model
0051In at least some embodiments, a payment model can be utilized to accommodate royalty payments that are to be made relative to digital objects, e.g. digital music that are consumed by end users. In the context in which digital objects comprise songs, consider the following. This is particularly useful in the event no metering data is available to indicate playcount.
0052For a given market such as the commuting market in which the user's mobile computing device comprises their in-dash unit, one can access the average commute time <T (min)> and the average listening time as a percentage of the commute time <p (%)>. Other assumptions in this model are: n minutes per song, and x copyright remuneration per song. In this model, the service provider can be responsible for daily payment to ASCAP of:
0000<br />Payment/day/subscriber=$(<<i>p>*<T </i>min>/<i>n</i>)*<i>x. </i>
0053As an example, assume that <T>25 minutes×2 round trips, p=80%, n=3 minutes, and x=$0.0007. Using these figures, monthly payments to ASCAP to cover copyright royalties would be $0.23.
0054Extensions
0055In at least some embodiments, the use of a signaling channel, as described above, can be extended as follows.
0056Often there are different user-associated or user-specific rights associated with digital objects, such as digital music, that constitute an agreement between a user and a particular service provider. These rights can include whether or not a user can transfer the digital object, how many times the user can consume the digital object, the resolution at which the digital object is to be consumed and the like. In these embodiments, the signaling channel can be used to convey or otherwise express these rights to the user's mobile computing device.
0057Alternately or additionally, the notion of synchronization can be applied to not only a user's personal library, but to synchronization with someone else's or some other entities remote library. For example, this might be the case in the context of digital objects that are shared amongst users or provided by various entities, e.g. music, blogs, blogs of groups to which the user belongs, syndication feeds such as RSS feeds and the like.
0058Additionally, the notion of synchronization can be extended to include synchronization of digital objects from a service provider's collection of objects, e.g. a remote library, based on a user's a priori selection. As an example, this might be daily news headlines or intra-day sporting alerts, such as would be provided through, for example, a syndication feed.
CONCLUSION
0059In various embodiments, a unidirectional broadcast network is utilized to provide digital content to users in a manner that allows users' computing devices to maintain synchrony with information that is relevant to the users. In at least some embodiments, the broadcast network utilizes a data channel and a signaling channel. The data channel is used for broadcasting data to various users, while the signaling channel—typically used for transmitting device or machine specific data—is used to transmit user-specific information associated with the information or data that the user finds interesting. This user-specific information can then be used by the user's mobile computing device to record such information or digital objects.
0060Although the invention has been described in language specific to structural features and/or methodological steps, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or steps described. Rather, the specific features and steps are disclosed as preferred forms of implementing the claimed invention.
Contents5
5 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2009252329A1 | Cited by | United States of America | Pre-grant |
| US2008148361A1 | Cited by | United States of America | Pre-grant |
| US2014195550A1 | Cited by | United States of America | Search report |
| US2007121651A1 | Cited by | United States of America | Pre-grant |
| US2009063645A1 | Cited by | United States of America | Pre-grant |
| US2014040941A1 | Cited by | United States of America | Pre-grant |
| US11003711B2 | Cited by | United States of America | Search report |
| US8819720B2 | Cited by | United States of America | Search report |
| US8752090B2 | Cited by | United States of America | Applicant |
| US8238559B2 | Cited by | United States of America | Search report |
| US2012272260A1 | Cited by | United States of America | Pre-grant |
| US2014195550A1 | Cited by | United States of America | Pre-grant |
| US8269813B2 | Cited by | United States of America | Search report |
| US8583758B2 | Cited by | United States of America | Applicant |
| US2009007176A1 | Cited by | United States of America | Pre-grant |
| US8243923B2 | Cited by | United States of America | Search report |
| US2011254911A1 | Cited by | United States of America | Pre-grant |
| US2009007171A1 | Cited by | United States of America | Pre-grant |
| US8621531B2 | Cited by | United States of America | Applicant |
| US2007124416A1 | Cited by | United States of America | Pre-grant |
| US10206002B2 | Cited by | United States of America | Applicant |
| WO2016153274A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US9084005B2 | Cited by | United States of America | Search report |
| US2014195550A1 | Cited by | United States of America | Search report |
| US2005058090A1 | Cites | United States of America | Pre-grant |
| US2005166257A1 | Cites | United States of America | Pre-grant |
| US2006069769A1 | Cites | United States of America | Pre-grant |
| US2008160910A1 | Cites | United States of America | Pre-grant |
| US6421358B1 | Cites | United States of America | Pre-grant |
| US6845230B2 | Cites | United States of America | Pre-grant |
| US7015972B2 | Cites | United States of America | Pre-grant |
| US7062779B1 | Cites | United States of America | Pre-grant |
21 members in 11 offices
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 55071006 | United States of America | A | |
| US20060550710 | – | – | – |
Members21
| Document | Office | Kind | |
|---|---|---|---|
| US2008098442A1 | United States of America | A1 | |
| AU2007349217A1 | Australia | A1 | |
| CA2661035A1 | Canada | A1 | |
| WO2008115283A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2008115283A3 | World Intellectual Property Organization (WIPO) | A3 | |
| EP2059898A2 | European Patent Office (EPO) | A2 | |
| KR20090067142A | Republic of Korea | A | |
| CN101529455A | China | A | |
| JP2010507350A | Japan | A | |
| ZA200900601B | South Africa | B | |
| EP2059898A4 | European Patent Office (EPO) | A4 | |
| RU2009114711A | Russian Federation | A | |
| US7853198B2 | United States of America | B2 | |
| AU2007349217B2 | Australia | B2 | |
| JP4886854B2 | Japan | B2 | |
| RU2449476C2 | Russian Federation | C2 | |
| BRPI0715774A2 | Brazil | A2 | |
| EP2059898B1 | European Patent Office (EPO) | B1 | |
| KR101465808B1 | Republic of Korea | B1 | |
| CA2661035C | Canada | C | |
| BRPI0715774A8 | Brazil | A8 |
71 transactions on the USPTO file
Allowed after 1 non-final rejection, 1 final rejection and 1 RCE.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Email NotificationEML_NTR | EML_NTR | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Examiner Interview Summary (PTOL - 413)MEXIN | MEXIN | |
| Examiner Interview Summary Record (PTOL - 413)EXIN | EXIN | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Miscellaneous Incoming LetterLET. | LET. | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Examiner Interview Summary (PTOL - 413)MEXIN | MEXIN | |
| Examiner Interview Summary Record (PTOL - 413)EXIN | EXIN | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Decision Made by Classification DivisionTI1052 | TI1052 | |
| Request for Classification Division DecisionTI1054 | TI1054 | |
| Miscellaneous Incoming LetterLET. | LET. | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Mail Post CardPST_CRD | PST_CRD | |
| Email NotificationEML_NTF | EML_NTF | |
| Application Is Now CompleteCOMP | COMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Initial Exam Team nnIEXX | IEXX |
7 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| Fee paymentFPAY | FPAY | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 20080098442
- Publication, DOCDB
- 2008098442
- Publication, EPODOC
- US2008098442
- Application
- 11550710
- Application, DOCDB
- 55071006
- Application, EPODOC
- US20060550710
Titles
- English
- Delivering Individualized Content Over a Broadcast Network
Classification
- CPC, 12
- H04N7/17318
- H04W8/18
- H04N21/242
- H04N21/26291
- H04N21/26606
- H04N21/41407
- H04N21/4623
- H04N21/472
- H04N21/4722
- H04N21/8133
- H04N21/8547
- H04W4/06
- IPC, 3
- H04N7 173
- H04N7 16
- G06Q30 00
- USPC, 6
- 725086000
- 348E07071
- 725062000
- 725087000
- 725112000
- 725113000