IV's 3D Printing DRM Patents and Applications

At recent International CES shows, I've been eyeballing 3D printer technologies and vendors.  Last October, Ryan Whitwam wrote that:

While you were busy getting yourself all worked up and declaring 3D printing the beginning of a new age, one of the most maligned figures in modern patent law is preparing to rain on your parade. Nathan Myhrvold, former Microsoft CTO and founder of patent holder Intellectual Ventures, has managed to get an expansive patent on 3D printing DRM. That 3D printing revolution we’ve been hoping for just got a lot trickier.

Turns out that the patents Whitwam references belong either to Searete, LLC or to The Invention Science Fund I, LLC, both apparently vehicles of Intellectual Ventures. Myhrvold is not listed as inventor.

Here is a list of Searete's and Invention Science's US patent and pending applications that address digital rights management and 3D printing and, more generally, secure manufacturing. Some pendings are continuations of the same specification and differ only in the claims. Nonetheless, this list does provide an overview into Intellectual Ventures' efforts in these areas.

8,286,236, "Manufacturing control system," assigned to The Invention Science Fund I, LLC.

Abstract

Methods and systems for a manufacturing control system include but are not limited to identifying at least one object data file configured to produce an object by a manufacturing machine; confirming that an authorization code is associated with the object data file, the authorization code configured to be received by the manufacturing machine, the manufacturing machine adapted to receive the authorization code; and enabling the manufacturing machine to interface with the object data file only if the authorization code meets one or more predetermined conditions.

20110178619, "Security-activated robotic tasks," assigned to Searete, LLC.

Abstract

Various methods and systems include exemplary implementations for a security-activated operational component involved in creating or producing or duplicating or processing or testing one or more objects. Possible embodiments include but are not limited to verifying an authorization to control a task or function of a robotic operation system, and responsive to the verification, enabling or disabling one or more operational components of the robotic operation system.

20100031351, "Security-activated production device," assigned to Searete, LLC

Abstract

Methods and systems for a security-activated production device include but are not limited to obtaining access to an object data file configured to produce one or more objects on the production device; verifying an authorization code associated with the object data file; and controlling operation of the production device to enable or prevent production of the one or more objects pursuant to the authorization code in accordance with one or more predetermined conditions.

20090292389, "Security-activated robotic system," assigned to Searete, LLC

Abstract

Various methods and systems include exemplary implementations for a security-activated operational component involved in creating or producing or duplicating or processing or testing one or more objects. Possible embodiments include but are not limited to verifying an authorization code to control a task or function of a robotic operation system, and responsive to the verification, enabling or disabling one or more operational components of the robotic operation system.

20090165127, "Authorization rights for operational components," assigned to Searete, LLC

Abstract

Various methods and systems include exemplary implementations for a security-activated operational component. Possible embodiments include but are not limited to obtaining access to an object data file configured to implement various functional operation regarding one or more objects; verifying validity of an authorization code associated with the object data file; and controlling operation of the operational component to enable or prevent its activation pursuant to the authorization code in accordance with one or more predetermined conditions.

20090165126, "Manufacturing control system," assigned to Searete, LLC.

Abstract

Methods and systems for a manufacturing control system include but are not limited to identifying at least one object data file configured to produce an object by a manufacturing machine; confirming that an authorization code is associated with the object data file, the authorization code configured to be received by the manufacturing machine, the manufacturing machine adapted to receive the authorization code; and enabling the manufacturing machine to interface with the object data file only if the authorization code meets one or more predetermined

20090164039, "Secure robotic operational system," assigned to Searete, LLC.

Abstract

Methods and systems for a secure robotic operational system include but are not limited to receiving an authorization associated with a directive to perform robotic operational tasks regarding one or more objects; verifying the authorization associated with the directive; and controlling operation of the robotic operational system via controlling a plurality of robotic elements, each robotic element of the plurality of robotic elements individually and/or in combination performing one or more functions in accordance with the authorization.conditions.

20090164379, "Conditional authorization for security-activated device," assignd to Searete, LLC.

Abstract

Various methods and systems include exemplary implementations for a security-activated operational component involved in creating or producing or duplicating or processing or testing one or more objects. Possible embodiments include but are not limited to obtaining access to an object data file configured to implement various functional operations regarding one or more objects; verifying validity of an authorization code associated with the object data file; and controlling operation of the operational component based on operational monitoring data processed by a verification module in accordance with a permission agreement and/or a licensing restriction.