For those who are too busy/lazy to go through the Draft Patent Manual, here is the full text of 3(k) which falls under Chapter IV titled, "Inventions not Patentable."
3(k) A mathematical or business method or a computer programme per se or
algorithms are not patentable.
4.11.1 A computer implemented invention mean any invention the performance of
which involves the use of computer, computer network or other
programmable apparatus, or an invention one or more features which are
realized wholly or partially by means of a computer programme/ programmes.
4.11.2 Computer programmes are a set of instructions for controlling a sequence of
operations of a data processing system. It closely resembles a mathematical
method. It may be expressed in various forms e.g., a series of verbal
statements, a flowchart, an algorithm, or other coded form and maybe
presented in a form suitable for direct entry into a particular computer, or may
require transcription into a different format (computer language). It may
73 merely be written on paper or recorded on some machine readable medium
such as magnetic tape or disc or optically scanned record, or it maybe
permanently recorded in a control store forming part of a computer.
4.11.3 If the patent application relates only to a machine i.e., hardware based
invention, the best mode of operation may be described along with the
suitable illustrations. However, in the case of a process related inventions ,
the necessary sequence of steps should clearly be described so as to
distinguish the invention from the prior art with the help of the flowcharts.
The source/pseudo/object codes may be incorporated in the description
optionally.
4.11.4 In order to distinguish the invention from the prior art, relevant prior art is
also required to be given in the specification. It is always essential to analyze
the invention in the light of what is described and the prior art, in order
to identify the contribution to the art and hence determine whether this
advancement resides in, or necessarily includes, technological features and
technical application or is solely intellectual in its content. A hardware
implementation performing a novel function is not patentable if that particular
hardware system is known or is obvious irrespective of the function
performed.
4.11.5 Applications related to computer inventions may broadly fall under the
following categories:
(a) Method/process:
(b) Apparatus/system:
(c) Computer program product.
The following aspects should be looked into while dealing with such applications.
4.11.6 The method claim should clearly define the steps involved in carrying out the
invention. It should have a technical character. In other words, it should solve
a technical problem. The claims should incorporate the details regarding the
mode of the implementation of the invention via. hardware or software,
for better clarity. The claim orienting towards a “process/method” should
contain a hardware or machine limitation. Technical applicability of the
software claimed as a process or method claim, is required to be defined in
relation with the particular hardware components. Thus, the “software per se”
is differentiated from the software having its technical application in the
industry. A claim directed to a technical process which process is carried out
under the control of a programme (whether by means of hardware or
software), cannot be regarded as relating to a computer programme as such.
For example, “a method for processing seismic data, comprising the steps of
collecting the time varying seismic detector output signals for a plurality of
seismic sensors placed in a cable.” Here the signals are collected from a
definite recited structure and hence allowable.
4.11.7 The apparatus claim should clearly define the inventive constructional
hardware features. The claim for an apparatus should incorporate a “process
limitation” for an apparatus, where “limitation” means defining the specific
application and not the general application. As a general rule, a novel solution
to a problem relating to the internal operations of a computer, although
comprising a program or subroutine, will necessarily involve technological
features of the computer hardware or the manner in which it operates and
hence may be patentable. For example, in a computer comprising means for
storing signal data and a first resistor for storing data, the clause starting with
“for” describes the function or process carried out by the apparatus, and form
the part of “process limitation” here.
4.11.8 The claims relating to software programme product are nothing but computer
programme per se simply expressed on a computer readable storage medium and
as such are not allowable. For example, if the new feature comprises a set of
instructions (programme) designed to control a known computer to cause it to
perform desired operations, without special adoption or modification of its
hardware or organization, then no matter whether claimed as “a computer
arranged to operate etc” or as “a method of operating a computer”, etc., is not
patentable and hence excluded from patentability. The claim might stipulate that
the instructions were encoded in a particular way on a particular known medium
but this would not affect the issue. e.g., A program to evaluate the value of PI or
to find the square root of a number are held not allowable. An invention
consisting of hardware along with software or computer program in order to
perform the function of the hardware may be considered patentable. e.g.,
embedded systems.
4.11.10 A mathematical method is one which is carried out on numbers and
provides a result in numerical form (the mathematical method or
algorithm therefore being merely an abstract concept prescribing how to
operate on the numbers) and not patentable. However, its application may
well be patentable, for example, in Vicom/Computer-related invention
[1987] 1 OJEPO 14 (T208/84) the invention concerned a
mathematical method for manipulating data representing an image, leading
to an enhanced digital image. Claims to a method of digitally filtering data
performed on a conventional general purpose computer were rejected,
since those claims were held to define an abstract concept not
distinguished from a mathematical method. However, claims to a method of
image processing which used the mathematical method to operate on
numbers representing an image can be allowed. The reasoning was that the
image processing performed was a technical (i.e. non- excluded) process
which related to technical quality of the image and that a claim directed to a
technical process in which the method used does not seek protection for
the mathematical method as such. Therefore the allowable claims as such
went beyond a mathematical method.
4.11.11 The patent application No.558/DELNP/2005 related to method of operating
the credential management processor. This was refused as it was found to be
attracting the provisions of section 3(k) as the alleged method was relating
to ‘receiving ‘, ‘de-referencing’ and ‘storing’ being purely a computer
implemented software application. As well as the enhancement of security
as claimed in method claims was already disclosed in the cited document
and is obvious to a person skilled in the art.
Showing posts with label software patent. Show all posts
Showing posts with label software patent. Show all posts
Wednesday, August 06, 2008
Sunday, July 27, 2008
Patent Office Meeting in Mumbai on 7th August: Please attend if you can
This is a call for FOSS developers in Mumbai who are interested in the software patents issue. The Patent office has called for a stakeholders meeting on the Draft Patent Manual.
On behalf of Red Hat, I have submitted our comments on the manual.
In 2005, I was involved in the Patent Amendment Act 2005 and on behalf of Red Hat, we had made representations to policy makers on why software patents are bad for the Indian software industry. At that time, Lawrence Liang and Prashanth Iyengar of the Alternative Law Forum had done a fantastic job of putting together a position paper on this issue virtually overnight. Happily, our lobbying was successful and software was kept out of the Amendment. What makes me hopping mad is that the Draft Manual seeks to bring in through the backdoor, something that was explicitly rejected by the Indian parliament. To say the very least, this is a very dubious practice.
Interestingly, Infosys and TCS are in favor of software patents. Those who followed the OOXML fight on this blog would know that both these organizations had voted in favor of Microsoft's OOXML proposal. If there are articulate FOSS developers in the Mumbai LUG, I would request them to be present at the 7th August 2008 meeting and explain to the group why software patents are against the interest of the developer community.
On behalf of Red Hat, I have submitted our comments on the manual.
In 2005, I was involved in the Patent Amendment Act 2005 and on behalf of Red Hat, we had made representations to policy makers on why software patents are bad for the Indian software industry. At that time, Lawrence Liang and Prashanth Iyengar of the Alternative Law Forum had done a fantastic job of putting together a position paper on this issue virtually overnight. Happily, our lobbying was successful and software was kept out of the Amendment. What makes me hopping mad is that the Draft Manual seeks to bring in through the backdoor, something that was explicitly rejected by the Indian parliament. To say the very least, this is a very dubious practice.
Interestingly, Infosys and TCS are in favor of software patents. Those who followed the OOXML fight on this blog would know that both these organizations had voted in favor of Microsoft's OOXML proposal. If there are articulate FOSS developers in the Mumbai LUG, I would request them to be present at the 7th August 2008 meeting and explain to the group why software patents are against the interest of the developer community.
Friday, July 25, 2008
Stakeholders Meeting on the Draft Patent Manual
Yesterday, the Ministry of Commerce and Industry hosted a "Stakeholders Meeting on the Draft Patent Manual." Around 70 people attended this meeting. The audience was a mix of lawyers, industry associations like CII, FICCI etc, civil society organizations and industry.
The pro-software patent lobby was pretty aggressive about their point of view. The body language made it apparent that they had come prepared for a fight. The main points of the pro-patents lobby (loosely paraphrased, since the discussion was happening so fast) were:
1) Patents will help Indian companies compete with the biggies globally
2) Indian companies are filing for patents abroad anyway, therefore we should have patents in India too.
3) Software patents are pro-innovation and should therefore be encouraged.
Prabir Purkayastha from the Knowledge Commons and myself represented the open source community. Prabir made the point that software is a form of mathematics and that merely applying it in a specific domain like image processing should not make it patentable. He also added that such patenting would be an incorrect interpretation of Section 3(K) which says that "a mathematical or a business method or a computer program per se or algorithms are not patentable."
At this point, the discussion became pretty heated and the chair of the meeting decided to call for a separate meeting on software patents. I'll keep you updated. Meanwhile, if there are open source supporters who are who can help us with the software patents issue, please let me know. If you happen to be based in New Delhi, that's even better! We need all the help we can get.
The pro-software patent lobby was pretty aggressive about their point of view. The body language made it apparent that they had come prepared for a fight. The main points of the pro-patents lobby (loosely paraphrased, since the discussion was happening so fast) were:
1) Patents will help Indian companies compete with the biggies globally
2) Indian companies are filing for patents abroad anyway, therefore we should have patents in India too.
3) Software patents are pro-innovation and should therefore be encouraged.
Prabir Purkayastha from the Knowledge Commons and myself represented the open source community. Prabir made the point that software is a form of mathematics and that merely applying it in a specific domain like image processing should not make it patentable. He also added that such patenting would be an incorrect interpretation of Section 3(K) which says that "a mathematical or a business method or a computer program per se or algorithms are not patentable."
At this point, the discussion became pretty heated and the chair of the meeting decided to call for a separate meeting on software patents. I'll keep you updated. Meanwhile, if there are open source supporters who are who can help us with the software patents issue, please let me know. If you happen to be based in New Delhi, that's even better! We need all the help we can get.
Subscribe to:
Posts (Atom)