IP Library Granted Patent US 10,455,020
Granted Patent B2
US 10,455,020 · App. 15/444,221 · Granted Oct 22, 2019

Systems and methods for managing and publishing managed content

Inventor: David Lerman (San Francisco, CA)
Assignee: SAY Media, Inc.
H04L67/1097G06F16/14G06F16/1873G06F16/219G06F16/2329H04L51/06H04L67/02H04L67/10H04L67/303H04L67/42
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,455,020
App. No.
15/444,221
Granted
Oct 22, 2019
Kind
B2
Abstract

Systems and methods for content management server systems configured to manage and publish managed content in accordance with embodiments of the invention are disclosed. In one embodiment, a versioned content management server system, includes a processor, a versioned content management application, managed content, wherein managed content includes content and content version metadata, wherein the versioned content management application configures the processor to receive updated content, locate managed content based on the received updated content, determine version data based on a portion of the located managed content, the received updated content, update the content version metadata data, associate the updated version content data with the managed content, receive a request for content, identify a portion of the managed content that corresponds to the requested content, retrieve the identified portion of the managed content, and transmit the retrieved portion of the managed content.

Claims (45)

1. A versioned content management server system, comprising:

a processor;

a content storage;

a memory connected to the processor and configured to store a versioned content management application, wherein the versioned content management application configures the processor to:

receive managed content comprising content and content version metadata;

store the managed content in the content storage;

receive a modified version of managed content;

locate the managed content stored in the content storage based on the received modified version of managed content;

determine version data based on a portion of the located managed content;

update the content version metadata based on the modified version of managed content and the version data;

update the managed content based on the differences between the modified version of managed content and the content within the located managed content;

obtain performance information from a system comprising of at least one of: a client display device and a content delivery server system;

locate the managed content based on the performance information;

update the content version metadata based on the performance information;

receive a request for content, wherein the request comprises a requested content version; and

transmit a portion of the managed content based on the requested content version.

2. The versioned content management server system of claim 1 , wherein the versioned content management application further configures the processor to update the managed content by updating the content and the content version metadata.

3. The versioned content management server system of claim 1 , wherein the versioned content management application further configures the processor to update the managed content by storing a second managed content in the content storage based on the updated content and the managed content, wherein the second managed content comprises second content and second content version metadata.

4. The versioned content management server system of claim 3 , wherein the managed content and the second managed content are arranged in a hierarchical relationship.

5. The versioned content management server system of claim 1 , wherein the versioned content management application further configures the processor to update the managed content by:

storing a second content within the managed content based on the updated content and the content of the managed content; and

updating the content version metadata.

6. The versioned content management server system of claim 5 , wherein the content and the second content are arranged in a hierarchical relationship.

7. The versioned content management server system of claim 1 , wherein the versioned content management application further configures the processor to update the managed content by incorporating the updated content into the managed content to create merged content.

8. A method for managing versioned content, the method comprising:

receiving managed content comprising content and content version metadata;

storing the managed content in a content storage;

receiving a modified version of managed content;

locating the managed content stored in the content storage based on the received modified version of managed content;

determining version data based on a portion of the located managed content;

updating the content version metadata based on the modified version of managed content and the version data;

updating the managed content based on the differences between the modified version of managed content and the content within the located managed content;

obtaining performance information from a system comprising of at least one of: a client display device and a content delivery server system;

locating the managed content based on the performance information;

updating the content version metadata based on the performance information;

receiving a request for content, wherein the request comprises a requested content version; and

transmit a portion of the managed content based on the requested content version.

9. The method of claim 8 , wherein updating the managed content comprises updating the content and the content version metadata.

10. The method of claim 8 , wherein updating the managed content comprises storing a second managed content in the content storage based on the updated content and the managed content, wherein the second managed content comprises second content and second content version metadata.

11. The method of claim 10 , wherein the managed content and the second managed content are arranged in a hierarchical relationship.

12. The method of claim 8 , wherein updating the managed content comprises:

storing a second content within the managed content based on the updated content and the content of the managed content; and

updating the content version metadata.

13. The method of claim 12 , wherein the content and the second content are arranged in a hierarchical relationship.

14. The method of claim 8 , wherein updating the managed content comprises incorporating the updated content into the managed content to create merged content.

Assignments (6)
SECURITY INTEREST Recorded Feb 24, 2020
From: MAVEN COALITION, INC.
To: FPP FINANCE LLC
Reel/Frame 051905/0156 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 20, 2020
From: LERMAN, DAVID ROSS
To: SAY MEDIA, INC.
Reel/Frame 051880/0088 →
CHANGE OF NAME Recorded Feb 20, 2020
From: SAY MEDIA, INC.
To: MAVEN COALITION, INC.
Reel/Frame 051980/0716 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 30, 2019
From: LERMAN, DAVID ROSS
To: SAY MEDIA, INC.
Reel/Frame 049324/0834 →
SECURITY INTEREST Recorded Oct 13, 2017
From: SAY MEDIA, INC.
To: SAY WHAT LLC
Reel/Frame 043858/0489 →
SECURITY INTEREST Recorded Sep 8, 2017
From: SAY MEDIA, INC.
To: SILICON VALLEY BANK
Reel/Frame 043533/0838 →
Continuity (3)
Continuation 15145685 · May 3, 2016
Continuation 13793738 · Mar 11, 2013
Related Publication 20170171312A1 · Jun 15, 2017