Hi. Let me rephrase my original question. Right now there are mixed rulings on whether software processes are patentable if you tie them to a general purpose computer (according to a web seminar on Bilski that I just took). Let's assume for the sake of argument that by hook or by crook, you can. Now consider software processes running in a client-server architecture. There would be a set of method claims in which all the steps are performed by the server machine. Similarly, there would be a set of method claims in which all the steps are performed by the client machine. Now what about the method claims in which some of the steps are performed by the server machine and some of the steps are performed by the client machine? Does the requirement of "a particular machine or apparatus" create a problem with the third set of method claims? In the spec, do I need to provide explicit support for [a system (comprising a server machine and a client machine) = a particular machine or apparatus]? Or is a method claim OK as long as each step is individually tied to some particular machine or apparatus, even though more than one particular machine or apparatus is involved? Thanks.
I examine networking stuff, so you may appreciate my opinion on the issue. You should get a Bilski rejection if the claimed method
covers one or more embodiments that can be performed completely mentally/verbally/physically by or between humans. 99% of Bilski rejections can be overcome by adding minor language to the preamble or the "things" in the method. It must be tied to at least one particular machine. It can be tied to more than one. The particular machine does not have to be the thing performing the method.
If you claim the following...
A method performed at a client, comprising:
Constructing a message;
Storing the constructed message in memory;
Transmitting the message to a server;
Waiting for a reply from the server; and
If a reply is not received from the server within a predetermined amount of time, retrieving the stored constructed message from memory and transmitting the message to a second server.
Barring explicit specification
definitions, you will get a Bilski rejection. Client = Person A; Server = Person B; Memory = Person A's memory; message = verbal sentence construct; transmitting = talking; waiting for reply = listening; retrieving from memory = recalling from Person A's memory. Notice I emphasized "definition". Examiners' definition for "definition" may be different than your attorney's definition for "definition".
You could, for instance, amend the above claim to limit the "a second server" to being a particular machine and do nothing with regard to "a client" or "a server" and still overcome the Bilski rejection. For example, adding the limitation "wherein the second server is a SIP gateway server" would overcome the Bilski rejection.
There is no requirement that each step be tied to a particular machine. Only one of the steps, OR, more commonly, recite enough structure in the preamble.
Hope that helps. Also note that in the networking realm, if you actually claim what your invention is, you will never run into a Bilski rejection.