IT patents for Russian software developers: benefits, problems, pitfalls

There are many myths around patents. Either they "do not work", then they are exacted for millions in compensation, then they refuse to patent, or vice versa "give out everything." Let's figure out how and why IT companies get patents, how not to get burned on them, when they are really needed and when not. Roman Tokarev, a leading specialist in patents at Yandex, will help us with this. 

My name is Alexey Bashuk, I am an intellectual property lawyer, patent attorney of the Russian Federation No. 2151. Roman Tokarev - patent attorney of the Russian Federation No. 2134. Roman recently spoke about IT patents at a conference in Skolkovo . After the conference, Roma and I phoned for a couple of hours and directly discussed all the possibilities and problems of Russian IT patents. This is how this publication came about.

If you are a developer or an IT entrepreneur, this article will help you understand how Russian laws protect you and your programs, what patents are issued for software solutions, what tasks these patents solve and what are the benefits of them, why the system is still far from ideal and how live it all. We will also go through the cases when patents are needed, when they are not needed, and if so, where to start.

Why protection of the source code of a program does not protect its meaning, logic and functionality in any way

Russian laws protect the source text and object code of computer programs, as well as the texts of books - by copyright ( clause 1 of article 1261 of the Civil Code of the Russian Federation ). 

Copyright protects only the form of the work, but not its essence: in The Lord of the Rings, the law protects the sequence of letters, not the idea of ​​a story about little people and a magic ring. It's the same with programs: if someone looks at my program and writes a similar one in another language, he will not violate my copyright. 

Copyright protects only the form of the work, not its meaning
Copyright protects only the form of the work, not its meaning

, , , , ? , . . 

, . . , , . , . , — , , , 10 5 (. 1406.1 ).

, : → → . : , « » (. 5 . 1350 ). 

, . — , — , . .

: , ,

— , . , , .

. , , , .

. : , , . 

— , « », , ; 

— , ;

, ;

— , .

1.

, . . 

, , , .

-, . , :

To make it easier for the patent office to understand the application, sometimes drawings are attached to the applications - the flowcharts themselves.
, — -.

2.

, , , , , - - . . 

, . .

3.

- , . , .

, , . , , : , .

« ». , «, …». « » — , , , .

  , , « », « » ( ), « ». , , , , .

— , ? ? 

— , , . - , , , . , , . , , . .

, , . , , . , - . , , — , .

Large companies are trying to patent both the method and the system and the devices themselves, to be sure.  If this cannot be done, then one is patented.
, , . , - .

, : , . - , .

— . — . 

, . , — , . .

1. .  . . , — . ,

2. . , , , . , , «» , . 

3. . , : , . 

, , , : — . — , . 

, , , , .   - : , , .

, :

  1. ;

  2. — , , .

— . .

4. . « » , «». . : , , . 

5. . — , . , , , . , . 

: , . , .

6. . , . , , . , , .

— , , - , ?

— . « ».  .

, - . , . , . , , .


, . . , , . – . , .

, — . . . , — , .

, . : , «» . «» : . — . 

, - , «» — (). , , - : , , . — . 

, , , , . , , , , . .

— , , , . , , . , « », , . , — .

: , . , . — , .


, . , , .

— . , , «» - . , . «».

— . , , . « », . — .

, - , . , , , . , , . , : . 

, , , . , , , , « , ».

— IT-

, , . , . 

, , , — . , , . , . 

, , . , .

-, , , , . , : .

. , , , . , , .

, — . , , , .

— , , , IT- ? ? 

— . . [ — , , , ].

  « ». – ,   — , , , , . , .

- : , . — , . .

, : . , , . , . , . , .

— , . , , , — . , . 

, – . — . – , , , .

— , - . , - . — . :

  1. , — . : -, -. 

  2. «» . 

  3. «discovery» — () . -, , , , , . — . , .

  4. , . , .

, — . , IT- , . - , , .

, ?

, — , . , , , . 

, , : , , . , , . .

, . . , .

— , , ? 

— , , , :) , - MVP, [ , ] :

) ; 

) ;

, . , . , , .

— , . : , - . 

, . - - - . - , , , .

- , , . , : , . .

, — . MVP . , , .

  1. , .

  2. , .

  3. . , , , - .

  4. . , , . , , .

  5. . . «», , . .

  6. , . . 

  7. . . .

, @bchlf.

, - «-». , , .

, :




All Articles