Your engineering team works tirelessly to build innovative platforms and tools. Filing a patent application is a natural next step to protect that hard work. Receiving a rejection from the United States Patent and Trademark Office can be incredibly frustrating.
Not every patent application is successful based on the initial submission. Software applications frequently face unique hurdles during the examination process. A rejection simply means the examiner found an issue with how the claims are currently drafted or supported.
Understanding the most common reasons for these setbacks allows you to approach the process strategically. Proper preparation helps you build a more resilient application from the very beginning.
Protect Your Innovations
Understanding Common Software Patent Rejections
Drafting an application for software inventions often leads inventors to confront a significant challenge known as the 35 U.S.C. Section 101 rejection. Section 101 sets the standard for what is considered patentable subject matter. The mistake held by many software inventors is thinking that the sheer ingenuity of their code or first-to-market advantage guarantees eligibility for a patent.
Since the landmark Alice Supreme Court decision, examiners follow a specific test to determine if an invention is directed toward a patent-ineligible abstract idea. If the claims point to an abstract idea, they need to add something extra that embodies an inventive concept. A clear articulation of how the software functions, improves computer functionality, or solves a specific technological problem is required to receive an allowance.
Rejections Beyond Eligibility
Applications that survive the Section 101 eligibility test can still face other statutory rejections. Examiners rigorously review claims for novelty, non-obviousness, and adequate description.
For example, an application may be rejected under 35 U.S.C. Section 102 if a single prior art reference matches each and every element of a patent application’s claim. This is known as an anticipation rejection. Rejections under Section 103 occur when the examiner considers the invention to be an obvious improvement over existing prior art. Finally, Section 112 rejections happen when there is a lack of adequate description. This means the claims fail to clearly define the subject matter. Vague functionality claims where the specification fails to adequately disclose the corresponding structure can trigger these rejections.
Support for Entrepreneurs
Strategies for Preparing Your Software Application
Taking a proactive approach before filing can significantly improve the strength of your application. Focusing on specific technical details is a useful way to begin the process of strengthening your claim.
- Define the technical solution. Avoid describing generic functionality or reciting conventional actions performed in a generic way. Detail the specific technical challenges others have faced and the inventive technical improvements implemented through your software.
- Identify the point of novelty. Ask yourself what technical improvement over existing technology your software will provide. Recognizing the unique functionality will help identify what specific features your software employs.
- Detail the system architecture. Merely reciting process steps in a way that is disassociated from the overall architecture of the system will generally not satisfy current disclosure requirements. You need to describe the overall computer architecture of the system within which the software will exist.
These elements provide the examiner with a clear picture of exactly what your engineers created. Supplying detailed flowcharts that break down the logic of the major routines and subroutines is also a highly effective practice.
Protecting Your Digital Assets
Your software is a valuable corporate asset. Turning complex code into a legally recognized property right requires precise translation. Patent examiners evaluate applications through a highly specific legal framework.
A thoughtful preparation strategy helps bridge the gap between engineering achievements and legal boundaries. Partnering with a skilled practitioner can be useful in crafting claims that accurately reflect your innovation while navigating complex patent office requirements.
Strategic IP for Established Companies
Disclaimer: The information provided in this article is for general informational purposes only and does not constitute legal advice. Accessing this information or contacting Patterson Thuente does not create an attorney-client relationship. You should not act upon this information without seeking professional counsel from a licensed attorney regarding your individual situation. Past results do not guarantee future outcomes.