{"id":32501,"date":"2017-07-12T10:41:56","date_gmt":"2017-07-12T14:41:56","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/multi-level-encryption-patent-survives-101-challenge-in-district-court-lexology-registration.php"},"modified":"2017-07-12T10:41:56","modified_gmt":"2017-07-12T14:41:56","slug":"multi-level-encryption-patent-survives-101-challenge-in-district-court-lexology-registration","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/encryption\/multi-level-encryption-patent-survives-101-challenge-in-district-court-lexology-registration.php","title":{"rendered":"Multi-level Encryption Patent Survives  101 Challenge in District Court &#8211; Lexology (registration)"},"content":{"rendered":"<p><p>    Introduction  <\/p>\n<p>    On May 23, 2017, the District Court for the Eastern District of    Virginia (District Court) denied a motion for summary    judgment that the patent claims asserted in a lawsuit brought    by TecSec, Inc. (TecSec) are invalid under 35 U.S.C.     101.[1]  <\/p>\n<p>    In the lawsuit, TecSec accused Adobe Systems, Inc. (Adobe) of    infringing four related patents[2]    directed to a multi-level encryption system that allows    encrypted objects [to] be nested within other [encrypted]    objects . . . resulting in multiple layers of    encryption.[3]    Representative Claim 1 from the 702 Patent is reproduced    below:  <\/p>\n<p>    Click     here to view the image.  <\/p>\n<p>    1. A method for providing multi-level multimedia security in a    data network, comprising the steps of:  <\/p>\n<p>    A) accessing an object-oriented key manager;  <\/p>\n<p>    B) selecting an object to encrypt;  <\/p>\n<p>    C) selecting a label for the object;  <\/p>\n<p>    D) selecting an encryption algorithm;  <\/p>\n<p>    E) encrypting the object according to the encryption algorithm;  <\/p>\n<p>    F) labelling the encrypted object;  <\/p>\n<p>    G) reading the object label;  <\/p>\n<p>    H) determining access authorization based on the object label;    and  <\/p>\n<p>    I) decrypting the object if access authorization is granted.  <\/p>\n<p>    Patent Eligibility Inquiry  <\/p>\n<p>    The eligibility inquiry under 35 U.S.C.  101 proceeds in two    steps.[4]    First, the court determines whether the patent claim at issue    is directed to one of the patent-ineligible concepts (e.g.,    abstract idea, law of nature, or natural phenomenon) (step    one).[5]    If the claim is not directed to a patent-ineligible concept,    the inquiry ends.[6]    Otherwise, the court determines whether the claim includes any    additional elements that transform the nature of the claim into    a patent-eligible application (step two).[7]    If a claim is found to be directed to a patent-ineligible    concept in step one and also lack any additional elements that    transform the nature of the claim into a patent-eligible    application in step two, the claim is ineligible for patent    protection under  101.[8]  <\/p>\n<p>    Arguments before the District Court  <\/p>\n<p>    Adobe argued that the claims in the asserted patents are    directed to the abstract idea of managing access to objects    using multiple levels of encryption.[9]    According to Adobe, Claim 1 of the 702 patent provides no    guidance at all as to how to encrypt an object, how to nest    objects, or any specific type of object that the process may    operate on and is thus abstract because it provides no    restriction on how the result is accomplished.[10]  <\/p>\n<p>    TecSec contended that Adobe failed to properly perform the step    one analysis by overgeneralizing the claims, failing to tie    the identification of the abstract idea to the claim language    at issue, and oversimplifying the claims and downplaying the    inventions benefits.[11]    Further, TecSec argued that there is no risk of preemption    because there are other ways to manage access to objects using    multiple levels of encryption that do not require an    [object-oriented key manager] component along with the recited    encryption and labelling steps.[12]  <\/p>\n<p>    District Courts Discussion  <\/p>\n<p>    Siding with TecSec, the District Court found that the claims in    the asserted patents are not directed to an abstract idea, law    of nature, or natural phenomenon.[13]    According to the District Court, the patent claims provide a    solution to a computer-centric problem that would not exist    but for the ubiquity of computer technology.[14]    Rejecting Adobes contention that the claims are reducible to    putting a sealed envelope (single-level encryption) into a    second sealed envelope (multi-level encryption) for extra    security, the District Court stated that the claims provide a    specific solution that allows multiple users in multiple    locations [to access] information at different security levels    from a central repository.[15]  <\/p>\n<p>    Further, the District Court noted that the asserted patents    preempt systems which make use of the specific method of an    object-oriented key manager without foreclos[ing] all forms    of multi-level security.[16]    Having determined that the patent claims are not directed to an    abstract idea, the District Court ended the patent-eligibility    analysis and denied Adobes motion for summary    judgment.[17]  <\/p>\n<p>    Takeaways  <\/p>\n<p>    This case illustrates that (i)     a solution that is necessarily rooted in computer    technology as illustrated in DDR[18]    and (ii)     evidence of no preemption as illustrated in McRO[19]    both continue to play an important role in helping patent    owners survive  101 challenges. When drafting claims, patent    applicants should carefully consider how the claims solve a    computer-specific problem without preempting all possible ways    of solving such a problem.  <\/p>\n<p>    On the other hand, patent challengers should emphasize how the    problem solved by the claims is a conventional one, and not one    that exists only because of the Internet or the computer    technology. Additionally, patent challengers should point out    why the claims impermissibly preempt an entire field of ideas.    Here, Adobe presumably had some difficulty arguing that    TecSecs claims cover all types of multi-level encryption    because Adobe also had to argue that its multi-level encryption    system did not infringe the asserted claims. In such cases,    patent challengers may want to, if possible, formulate the    abstract idea in a way that does not include their own    products.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>See more here:<br \/>\n<a target=\"_blank\" href=\"http:\/\/www.lexology.com\/library\/detail.aspx?g=6034a23a-c2d9-4103-9eb2-73bc03ed4054\" title=\"Multi-level Encryption Patent Survives  101 Challenge in District Court - Lexology (registration)\">Multi-level Encryption Patent Survives  101 Challenge in District Court - Lexology (registration)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Introduction On May 23, 2017, the District Court for the Eastern District of Virginia (District Court) denied a motion for summary judgment that the patent claims asserted in a lawsuit brought by TecSec, Inc. <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45],"tags":[],"class_list":["post-32501","post","type-post","status-publish","format-standard","hentry","category-encryption"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/32501"}],"collection":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/comments?post=32501"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/32501\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=32501"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=32501"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=32501"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}