Modern software teams build competitive advantage not just from clean code but from technical effects their systems achieve—faster consensus on distributed nodes, reduced inference latency at the edge, resilient data pipelines under real-world constraints. Whether to patent such work is not a question about “code” as text; it is a question about functional innovations that solve technical problems. In Uzbekistan,  the law on the Legal Protection of Computer Programs and Databases clearly separates the types of protection available for software. It grants copyright protection to computer programs and databases, but only covers the original expression of code—not the underlying ideas, algorithms, or principles.  However, article 6 of the The Uzbek Inventions Law software can be part of a patentable invention—provided it’s presented as a technical system or method that achieves a technical effect, thus solving a technical problem. Understanding that line—and timing disclosures accordingly—can decide whether your next release creates a moat or an invitation for fast followers.
Copyright protects the expression of a program—your source and object code—automatically at creation. Program Protection Law – Uzbekistan’s dedicated statute on computer programs and databases – adopts this principle and makes registration optional but evidentiary, useful when you later need to prove authorship or ownership. What copyright does not protect is the underlying functionality or algorithms—others may re-implement the same method in different code without infringing. That functional gap is where patents enter.
Patents exist to protect technical solutions to technical problems. Most modern patent systems converge on a similar approach for software: programs “as such” are excluded, but software-implemented inventions that produce a concrete technical effect (e.g., lower cache-miss rate on specified hardware; fewer messages for Byzantine consensus; measurable improvement in network stability) are eligible when they also satisfy novelty, inventive step, and industrial applicability. WIPO’s policy materials ground this in TRIPS Article 27’s technology-neutral standard, even as national laws define the contours of excluded subject matter.

Patentability of software-implemented inventions in Uzbekistan

• The statutory baseline

Uzbekistan’s Inventions Law sets the core tests: an invention must be new, involve an inventive step, and be industrially applicable. The statute also codifies a six-month grace period for disclosures by the inventor or applicant—critical for teams that present at meetups or push to GitHub before filing. Terms are 20 years for inventions (extendable up to 5), 5+3 years for utility models, and 10+5 years for industrial designs.
Crucially for software, algorithms and programs for electronic computers appear in the list of subject matter not recognized as inventions—but that exclusion targets “software as such,” not software-implemented methods or systems that solve a technical problem. On the other hand, The Uzbek Inventions Law defines patentable inventions as either a product or a method that performs actions on material objects using material means (Article 6). At the same time, it excludes algorithms and computer programs as such from patentability. Therefore, while software per se (code or algorithms alone) is not patentable, it may become part of a patentable invention if described as a technical method or system implemented using a computer (a material device) that produces a technical effect or solves a technical problem. Though this specific phrasing isn’t in the law verbatim, it accurately reflects the interpretation based on Article 6’s structure and exclusions. Thus, in practice, applicants draft claims to the method carried out by a processor and/or the system configured to execute it, emphasizing the technical effect with evidence and benchmarks.

• Procedure and timing

Patent applications are examined by the Agency for Intellectual Property under the Ministry of Justice. After filing and formal examination, Uzbekistan requires a scientific and technical examination on the merits for inventions—this must be requested within three years of the filing date, or the application is treated as withdrawn. Temporary legal protection begins upon publication of the application for an invention as per the Inventions Law. These timing levers matter for roadmap planning and disclosure control.

• Enforcement context

Published patent litigation in Uzbekistan remains infrequent, and courts often rely on technical opinions from state bodies. That makes front-loaded technical evidence—reproducible tests, system logs, and profiling data—especially important both in prosecution and in any later dispute. While specialized patent courts do not exist, enforcement proceeds in civil or commercial courts under general evidentiary rules.

• Territorial planning

Uzbekistan is a member state of Patent Cooperation Treaty (PCT), so you can file a PCT to preserve options and later enter the national phase. It is not a member of the Eurasian Patent Convention, so Eurasian patents do not extend protection to Uzbekistan; plan on national filing.

Recent judicial practice shaping “software patents” (selected authorities)
While Uzbekistan has limited published case law on software patentability per se, international jurisprudence offers clear signposts on what courts consider a technical contribution versus an abstract idea:

• United States (Supreme Court): Alice Corp. v. CLS Bank (2014) introduced a two-step framework that invalidates claims directed to abstract ideas—including business methods—unless they add an inventive concept beyond implementing the idea on generic computers. This case continues to shape U.S. eligibility analysis for software claims.
• Europe (EPO Boards of Appeal): T 641/00 (COMVIK) established that only technical features count toward inventive step; non-technical features (e.g., business constraints) may appear in the claim but cannot support inventiveness. The EPO’s current Guidelines synthesize this approach for CII.
• India (Delhi High Court): Ferid Allani v. Union of India (2019) confirmed that CRIs (computer-related inventions) can be patentable when they show technical effect/technical contribution, even if implemented by software—nudging practice away from a categorical bar on “software per se.
• These authorities align with Uzbekistan’s statutory exclusion of “programs for electronic computers” as inventions in themselves, while leaving room for software-implemented technical solutions framed as methods or systems with demonstrable technical effects.

Comparative page: how other jurisdictions treat software-implemented inventions

European Patent Office (EPC states). Programs “as such” are excluded (Art. 52(2)), but if a claim solves a technical problem with technical means, it is patent-eligible. Under COMVIK, only technical features contribute to inventive step. Practical tip: anchor claims to system architecture, resource management, or hardware-bound constraints and present performance evidence.
United Kingdom: The UKIPO applies the Aerotel/Macrossan four-step test to ask whether the contribution is solely within excluded matter and, if not, whether it is technical. Recent UKIPO Manual updates (April 2025) refine guidance for computer-related inventions and emphasize articulating the technical contribution clearly. 
United States: Section 101 eligibility turns on the Alice/Mayo two-step: (1) is the claim directed to an abstract idea? If so, (2) does it include an inventive concept transforming the idea into patent-eligible subject matter? Claims that merely “do it on a computer” fail; claims improving the functioning of the computer itself can pass (e.g., specific memory or network improvements). Draft with concrete architectures and non-generic components. 
India: Section 3(k) excludes “computer program per se,” but the CRI Guidelines and the Ferid Allani decision steer practice toward allowing claims that show a technical effect or technical contribution, especially when tied to novel hardware interactions or measurable system improvements. 
China: The 2024 revision of the Examination Guidelines further clarifies protection for inventions “involving computer programs,” especially in AI/big-data contexts, when claimed as technical solutions with program features cooperating with technical means to achieve technical effects. Expect a fact-intensive analysis; provide implementation details and data.Uzbekistan (for comparison). The law expressly excludes algorithms and programs as inventions, but practice permits software-implemented methods and systems that meet the triad of patentability and show technical effect—conceptually close to the EPO/India positions and practically compatible with evidence-driven drafting techniques.

Practical guidance for engineering teams (why, when, and how)
From an engineering vantage, a software patent in Uzbekistan (and elsewhere) is most compelling when you can demonstrate causality: that the claimed steps produce a technical effect because of your design choices, not merely as a by-product of using a generic computer. The European Patent Office’s well-developed doctrine on computer-implemented inventions (CII) —while not binding in Uzbekistan—offers a useful mental model for drafting: define the features essential for the technical effect and exclude non-technical business logic from driving inventiveness. Internal benchmarks and profiling reports become exhibits in your argument.
Given the six-month grace period, teams that have already disclosed should triage quickly, gather proof that the disclosure came from the applicant/author, and file before the window closes. For incremental engineering improvements with limited runway, consider a utility model to obtain quicker, narrower protection while continuing R&D toward a full invention filing. 

Uzbekistan-specific checklist:

1. Map the effect: Tie your feature to measurable system-level improvements under realistic workloads; keep versioned evidence. This supports both patentability and later enforcement.
2. Control disclosure: Use the six-month grace wisely; if a talk or repo is imminent, file first or file quickly thereafter, documenting provenance of the disclosure. 
3. Choose the vehicle: For crown-jewel methods, pursue an invention patent; for incremental improvements, consider a utility model while you iterate.
4. Plan geography: Use PCT, but remember Uzbekistan requires national protection (no Eurasian patent coverage).

ConclusionFor engineering-driven companies operating in or targeting Uzbekistan, the right question is not “Can I patent code?” but rather “Does my system solve a technical problem in a non-obvious way, and can I prove it?” If the answer is yes—and you manage disclosures carefully—Uzbekistan’s patent framework allows protection for software-implemented inventions, complemented by automatic copyright in the program text and trade secret controls for sensitive operational know-how. Align your IP actions with release cadence and roadmap realities: file first when you can, marshal your benchmarks, and draft claims that reflect the technical contribution your engineers actually built. 
At our law firm, we work closely with software developers and startup founders, and IT entrepreneurs to navigate these complexities. From assessing patentability to drafting applications and coordinating multi-jurisdictional strategies, our goal is to ensure that your innovations receive the protection they deserve—both in Uzbekistan and globally.

DISCLAIMER:
The information provided in this article is of a general nature only and is intended to familiarize you with the matters of your interest.  The effect and application of laws may vary depending on the specifics of your particular situation. Due to the changing nature of laws, regulations and norms, You should not rely, for legal advice, on statements or representations made within the Website. If you need legal advice upon which you intend to rely during your legal affairs, please consult us.
 
Gulnoza Abdurakhmonova