All Things Pros focuses exclusively on patent prosecution. The blog uses PTAB decisions, and the prosecution history that led to appeal, to discuss good and bad strategies for handling 102, 103, 101 and 112 rejections. Claim construction using Broadest Reasonable Interpretation is also a major focus. And sometimes you'll find prosecution topics such as after-final, RCE, and restriction practice.

Tuesday, November 23, 2010

Takeaway: In Ex parte Smotkin, the applicant appealed a claim to a fuel cell membrane including a coating having a thickness described in the claim as "in the range shown for Nafion 117 in Figure 10." Figure 10 was actually reproduced as part of the claim, rather than the claim referring to a figure in the spec. The BPAI found that the claim was not indefinite. The Board distinguished Ex parte Fressola, which generally prohibits a claim from incorporating by reference to the specification or drawings. The Board found that the appealed claim did not incorporate by reference, but rather "displays the figure and pinpoints the elements of the figure that relate to the limitations of the claim."

84. A proton-conducting membrane designed to serve as an electrolyte in a fuel cell, which membrane consists essentially of
a single metal or metal hydride support, wherein
one or both faces of said support is coated with an electronically-insulating proton-conducting coating, which coating consists of an inorganic material that contains no liquid phase, said coating having a thickness such that the ASR for protons at at least one temperature between 220°C and 550°C is in the range shown for Nafion® 117 in Figure 10:

In the Final Rejection, the Examiner rejected claim 84 as indefinite, citing to MPEP 2107(s):

Incorporation by reference to a specific figure or table "is permitted
only in exceptional circumstances where there is no practical way to
define the invention in words and where it is more concise to
incorporate by reference than duplicating a drawing or table into the
claim. Incorporation by reference is a necessity doctrine, not for
applicant's convenience." Ex parteFressola, 27 USPQ2d 1608, 1609 (Bd. Pat. App. & Inter. 1993) (citations omitted).
(Emphasis in original.)

The Examiner further explained that:

In this instance, it is pointed out that a first set of claims (i.e. claims 75-82) has been properly delineated and set forth without the use of said table/fimre. Accordingly, it is contended that is not imperative or necessary to specifically define the claimed subject matter by using the table/figure. The examiner is also concerned about the possibility that claim 84, as now amended, be technically inaccurate due to the use of a table/figure subject to multiple interpretations.

In the Appeal Brief, the Applicant noted a difference between claim 84 and the set of claims which did not use a figure:

[T]he range set forth in the graph of claim 84 is different from that mandated by claim 75; claim 75 mandates an area-specific resistance for protons (ASR) of 0.01-100 C2.cm2 whereas the range shown for NafionB in Figure 10 has a lower limit somewhat greater than 0.01 C2.cm2 and an upper limit clearly lower than 100 C2.cm2. As the figure is the only place where this range for NafionB is set forth in the specification, it is believed necessary to incorporate the figure into the claim in order to provide adequate support for this range.(Emphasis added.)

The Applicant also distinguished Ex parte Fressola, arguing that Fressola involved an omnibus claim ("as disclosed in the specification and drawings herein") whereas the claim on appeal "sets forth the drawing and identifies the portion of the drawing that is relevant to the limitation of the claim."

The Board reversed the indefiniteness rejection:

In Ex parte Freessola we held that “[i]ncorporation into the claims by express reference to the specification and/or drawings is not permitted except in very limited circumstances.” Claim 84 "does not incorporate by reference a figure or table, it
displays the figure and pinpoints the elements of the figure that relate
to the limitations of the claim." (Appeal Brief 9.)

My two cents: The Board did not address the Examiner's concern with "use of a
table/figure subject to multiple interpretations." Or the Applicant's
characterization of Fressola as being about an omnibus claim rather than
a figure in a claim. I checked out Fressola, and its facts really were about an omnibus claim: "as disclosed in the specification and drawings herein". But Fressola does contain a long discussion of other case law (going back to 1943) dealing with incorporation by reference of figures or tables.

The claim here literally included the figure, where Fressola prohibits incorporation of a figure by reference. But even if Fressola were applied here, it seems to me Fressola's exception might apply:

Incorporation by reference to a specific figure or table is permitted
only in exceptional circumstances where there is no practical way to
define the invention in words and where it is more concise to
incorporate by reference than duplicating a drawing or table into the
claim.

Monday, November 22, 2010

Last week the PTO released a Notice of Proposed Rulemaking for rules governing ex parte appeals before the BPAI. (Read the official notice here.)

Generally, these rules make the applicant's job easier. The PharmaPatents blog has a nice summary here, so I won't bother with one. I will also tell you my personal favorite among all the changes: Summary of the Claimed Subject Matter. The current rule requires an explanation of each limitation of each claim under appeal. The proposed rule requires only an explanation of "each limitation in dispute by appellant." Less work for me and a reduced file wrapper as compared to the current practice.

I'm also glad to see a detailed explanation – almost three pages – of what constitutes a new ground of rejection in an Examiner's Answer. Five examples of what does constitute a new ground and five examples of what does not. While I don't particularly like the "not a new ground" list, I'm happy to have guidance from the PTO rather leaving this up to the Examiner's interpretation. While this guidance is not part of the text of the rule itself, I would confidently refer to the Federal Register Notice when arguing that the Answer did contain a new ground, if it came to that.

Past History: As you may recall, the PTO suspended the last proposed package of appeals rules. That package was supposed to go into effect December 2008, but ended up suspended after significant comment from patent practitioners. The currently proposed rule package bears little resemblance to the last one –which is a good thing.

Wednesday, November 17, 2010

Takeaway: In Ex parte Bayley, the BPAI affirmed an obviousness rejection because "an airbag inflatable to a first
pressure ... determined from a graph that plots pressure versus
thickness" did not distinguish the airbag from any other airbag. The BPAI found that the pressure determination limitation was not a structural limitation, and thus did not give it patentable weight.

The claims were directed to a vehicle airbag system. The limitation at issue (emphasized below) related to the pressure used to inflate the airbag.

19. A system for helping to protect an occupant of a vehicle ... said system comprising:
an inflatable vehicle occupant protection device ... ; and
an inflation fluid source actuatable to provide a volume of inflation fluid to said inflatable volume sufficient to inflate said inflatable vehicle occupant protection device to at least a first pressure, said first pressure being determined from a graph that plots pressure in said inflatable vehicle occupant protection device versus said thickness of said inflatable vehicle occupant protection device ...

The Examiner rejected claim 19 as obvious. The Examiner relied on one reference to teach a relationship between inflation pressure and airbag thickness, and another reference to teach all the other elements.

The Examiner indicated that no patentable weight was given to using a graph to determine the inflation pressure. The Examiner characterized this use of a graph as merely “an intermediary step in a design process” and “not germane to the patentability of the apparatus because there is no structure that is imparted by the design step that distinguishes the airbag claimed from the prior art airbag.”

In the Appeal Brief, the Applicant argued that the graphically determined inflation pressure was a structural rather than a process limitation and should therefore be given patentable weight. Specifically, the Applicant argued that the limitation of a “graphically approximated pressure” should be interpreted as a structural limitation because it defines the pressure of the inflation device, which is “an objectively observable characteristic of the device.” According to the Applicant, the relationship embodied by the graph “imparts upon the protection device a particularized inflation pressure depending on the thickness of the airbag.”

The Applicant went on to explain similarities between the limitation of claim 19 and other types of limitations, all of which the Applicant said were structural:

Claim 19 recites the structural limitation of a pressure that is determined graphically. More specifically, the structure recited in claim 19 is that of a protection device and an inflator that provides a volume of inflation fluid sufficient to inflate the protection device to at least a first pressure, the magnitude of which is approximated from a plotted point on a graph that plots the inflated thickness of the protection device versus the inflated pressure of the protection device. This structure cannot be described in any other way and therefore must be given patentable weight.
The scope of this claim element is no less structural, and therefore no less germane to patentability, than a recitation of a specific pressure (e.g., 20 psi/g), a specific formula (e.g., pressure equal to a mathematical formula based on thickness), or a specific function (e.g., a pressure sufficient to prevent an object from striking through the inflated thickness of the protection device).

The Board was not persuaded, deciding that "an inflation pressure value determined from a plot of inflation pressure versus airbag thickness" was not a structural limitation. Referring to the Appeal Brief's list of alternative ways to express the function of inflating, the Board explained that:

Appellants have not provided any evidence to show that an airbag having an inflation pressure chosen from a plot of inflation pressure versus airbag thickness is any different structurally from an airbag having an inflation pressure chosen from a table of inflation pressures and airbag thicknesses or an airbag having an inflation pressure and airbag thickness derived experimentally. An attorney's arguments in a brief cannot take the place of evidence. In re Pearson, 494 F.2d 1399, 1405 (CCPA 1974).

The Board then affirmed the obviousness rejection.

My two cents: I think the Board's point – the airbag in the claim is not different than the airbag in the reference – is very important. But it's also subtle. The distinction (presumably) is the actual mechanism used to inflate to the desired pressure – but that mechanism wasn't actually claimed.

What's going on here is what I call "inferential claiming." The Applicant claimed around the mechanism for inflating to a desired pressure, by referring to an inflation value that was determined in a specific way (a graph). But the claim did not expressly recite the mechanism.

How should the claim have been drafted? Let's assume that software running on a processor determined the desired inflation pressure based on airbag thickness. Then the claim should recite the processor as a structural element, and use functional language to describe how the processor controls the inflation. Maybe even throw in more structure, in the form or an actuator or valve, controlled by the processor.

Now, I'm not suggesting that my improved claim is patentable over the references. If you throw in a reference that teaches processor-controlled inflation, the Applicant's inflation mechanism may well be obvious in light of the relied-upon reference that taught a relationship between thickness and pressure.

What I am saying is it's a really good idea to make sure the novel mechanism is actually expressed in the claim.

I'll mention one more criticism I have of the claim as written: the use of "a graph" in the claim. The way I see it, the software doesn't literally use a graph to determine inflation values. A table, maybe. A graph, no. So I'd stay away from "graph" and claim the software using a functional relationship between pressure and thickness.

Monday, November 15, 2010

Takeaway: In a 1986 claim construction decision, the Federal Circuit held that a method claim which referred to "engaging eight cube pieces" was limited to a 2x2x2 cube despite the use of "which comprised" in the method preamble. Furthermore, the cube size was not expanded by the use of "comprising" in one of the steps: "rotating a first set of cube pieces comprising four cubes about a first axis." The court found that "comprising" was not used as a transitional phrase when describing the first set. Moleculon Research Corp. v. CBS, Inc. (Moleculon II), 793 F.2d 1261 (Fed.Cir. 1986). An old case, but an important one.

This is a claim construction and literal infringement case. The method claim at issue involves a solution for what you may recognize as a mini Rubiks' cube.

3. A method for restoring a preselected pattern from sets of pieces... which comprises:
a. engaging eight cube pieces as a composite cube;
b. rotating a first set of cube pieces comprising four cubes about a first axis;

The accused products included the classic Rubik's cube and the super Rubik's cube. The classic cube included 27 pieces (3 x 3 x 3), where you rotate 9 at a time. The super cube included 64 pieces (4 x 4 x 4), where you rotate 16 at a time.

The district court found that even though the larger cubes were not 2 x 2x 2, infringement was nonetheless present because claim used the magic word "which comprises" in the preamble:

Claim 3, and its dependent claims, 4 and 5, read on the 2 × 2 × 2 form of the puzzle, as well as on such larger cubic embodiments as the 3 × 3 × 3 and the 4 × 4 × 4, because it employs the open transitional phrase "which comprises." The term "comprising" denotes a patent claim as being "open," meaning that the recitation of structure in the claim is open to additional
structural elements not explicitly mentioned.
(Emphasis in original.)

The patentee (Moleculon) argued that "which comprises" in the preamble allowed for larger cubes:

Moleculon counters that using the transitional phrase "which comprises" not only opens the claim to additional steps, but also opens the claim and its individual method steps to additional structural elements.

The Federal Circuit held that the 3 x 3 x 3 cube did not infringe.

In considering the patentee's argument about the transition in the preamble, the court concluded that "the transitional phrase does not, in the present case, affect the scope of the particular structure recited within the method claim's step." The court didn't find the accused infringer's "missing step" argument persuasive either, noting that the step wasn't missing, merely different.

The court framed the issue as the effect of the structural limitation, within the step, on the cube size:

[Step a] ("engaging eight cube pieces as a composite cube") contains a structural recitation ("eight cube pieces"). The question before us is not whether, because of the transitional phrase "which comprises," the step reads on a step of an accused method which recites additional structure (hypothetically, "eight cube pieces and six metal plates"), but rather whether this step which recites engaging "eight cube pieces as a composite cube" reads on a step which engages more than eight cube pieces as in the 3 × 3 × 3 Rubik's Cube or the 4 × 4 × 4 Rubik's Revenge.

After referring briefly to district court decisions where structural recitations in a method claim step were construed as limitations, the court held that:

[C]laim 3 is limited, at least for purposes of literal infringement, to a method for restoring a 2 × 2 × 2 composite cube. That interpretation follows not only from the language of step (a), but also from the way the eight cube piece composite cube is manipulated in steps (b), (c), and (d). These steps are limited to manipulating sets of four cubes only.

With regard to step (b), the court noted the use of "comprising" in that step didn't help the patentee either because it wasn't used as a transitional phrase:

During oral arguments, Moleculon argued that the word "comprising" in step (b) ("rotating a first set of cube pieces comprising four cubes about a first axis") means that the step covers four cubes or more. "Comprising" is not used here as a transitional phrase and has no special legal effect as such. Hence, it should be interpreted according to the normal rules of claim interpretation. No analogous word precedes the structural recitation of the number of cube pieces in steps (a) and (c). "Comprising" in step (c) reasonably interpreted means "having" but not "having at least."

Having found that the district court's interpretation was erroneous, the court vacated the finding of infringement. However, the court then remanded because the district court didn't make any findings about how the doctrine of
equivalents applied to the larger 3 × 3 ×3 cube.

Postscript: On remand, the district court found that the method claims were directly infringed, through the doctrine of equivalents, by users playing the 3x3x3 cube. Moleculon Research Corp. v. CBS, Inc., 666 F.Supp. 661 (D.Del.1987) (Moleculon III). However, the Federal Circuit reversed, finding that the district court's analysis "entirely reads the number of cubelets and their corresponding engagement/rotation out of every step of the claim."

My two cents: I agree with this analysis. I see it as a good case for accused infringers and a bad one for patentees. But the Federal Circuit hasn't always used Moleculon II in this way.

Yet the Federal Circuit cited Moleculon II years later for the unremarkable proposition that "open language of claim 1 embraces technology that may add features to devices otherwise within the claim definition." Gillette Co. v. Energizer Holdings, Inc., 405 F.3d 1367 (Fed. Cir. 2005). Sure, this is a general statement of the law – that's why I said it was an unremarkable proposition – but it's not really what Moleculon II was about. The court in Gillette went on to find that "a group of first, second, and third blades" could include
additional blades because the apparatus preamble used the transition
"comprising." That's the opposite of Moleculon II, as pointed out by the dissent in Gillette.

There are differences in the three cases, of course, which can perhaps be used to reconcile them. Moleculon II didn't look to anything but the plain language of the claims to reach its result. Spectrum reached the same result as Moleculon II after examining statements made during prosecution. Gillette reached the opposite result as Moleculon II after examining the specification, several other claims, and the prosecution history.

Takeaway: Most of the BPAI decisions that are appealed to the Federal Circuit involve fairly routine reviews of prior art rejections. In re Jung is different: it's about the Examiner's requirement to make a prima facie case. As such, In re Jung has the potential to greatly impact patent prosecution. As elegantly put in Jung's brief, when the Examiner does put forth of a prima facie case, "applicants are sufficiently informed as to the full basis of the rejection ... and applicants can determine how to best proceed during initial prosecution." But if the BPAI doesn't provide an independent review of the prima facie case requirement, "applicants are all but required to prophylactically submit rebuttal evidence against uncertain and shifting grounds of rejection."

I've been following this case since the appeal was filed, and have read the briefs to the Federal Circuit (available from Westlaw or Lexis) as well as most of the file history (on PAIR: Appl. No. 10/770,072). Oral arguments took place a couple of weeks ago. Here are my thoughts on this interesting case.

Summary:
In Jung's brief, he asks the Federal Circuit to decide an issue of first impression: whether the BPAI properly ruled on the merits of an anticipation rejection instead of ruling on the appealed issue of whether the Examiner had made a prima facie case of anticipation. Jung's brief further defines the prima facie case of anticipation as having two requirements: (i) the Examiner must construe the claims under the broadest reasonable interpretation standard; and (ii) the Examiner must "adduce sufficient evidence to bridge any facially apparent 'teachings' of the applied reference."

The PTO doesn't see it this way. In the PTO's brief to the Federal Circuit, the Solicitor frames the issue as a routine review of a BPAI decision: "whether a reasonable claim construction and substantial evidence support the Board's conclusion that the prior art, Kolinksy, anticipates Jung's claim 1."

I don't know how much leeway the Federal Circuit has in choosing between issues. As a patent prosecutor, I hope the Federal Circuit does take up the issue of a prima facie requirement. But if the Federal Circuit wants to avoid the issue, I think it can do so on the grounds that Jung didn't properly raise the issue below. The PTO makes a convincing case that Jung did not challenge the prima facie case before the Examiner or before the BPAI, but instead substantively responded to the merits of the rejection. Thus, it seems to me that Jung may have waived his right to argue the prima facie requirement issue on appeal to the Federal Circuit.

Moreover, I think that Jung loses even if the Federal Circuit takes up the issue. That is, I think the Examiner did present a prima facie case. The claim term at issue was "well-charge-level controller." The Examiner explained that he gave each of the words their ordinary meaning, and explained how the reference taught a device that controlled the level of charge in a well.

That said, I am thrilled that Jung, even with these bad facts, took this issue up to the Federal Circuit. Because the PTO's idea of prima facie case – as expressed in the Solicitor's brief – is not enough. The way I read the brief, the PTO has taken the position that the Examiner produced a prima facie case of anticipation merely by: i) asserting that every claim limitation was disclosed by the reference; and ii) clearly designating what part of the reference was relied on. I dunno about you, but I need more than that to mount a good attack on a rejection. I want what Jung wants – explicit claim construction and an explanation of how the words used in my claim are met by the words used in the reference.

Wrap-up: I'll post again when the court releases its decision. The court may choose not to provide a full opinion. I'll be very disappointed if the opinion is nothing more than a bare Rule 36 affirmance. This case deserves at least a Rule 36 affirmance with a short explanation of the grounds of decision, since there is such a discrepancy between how the two parties framed the issues.

Thursday, November 11, 2010

Takeaway: In Ex parte Tipley, the claims described physical parts "configured to" move in a specified manner. The Examiner acknowledged that the reference did not teach parts configured to move as claimed. The Examiner insisted that the reference nonetheless anticipated by treating "configured to" as "capable of" and further insisted that the parts in the reference could move as claimed. The Board treated this as an inherency argument. The Board then found that the Examiner's understanding that the parts could move was simply speculation. Since speculation is not enough to support inherency, the Board reversed the anticipation rejection.

The claims were directed to an arrangement of circuit boards in a computer. Two of the appealed claims are shown below, with the limitations at issue being highlighted:

5. A computer system comprising:
a first circuit board comprising a
first connector;
a second circuit board ... having a second connector couplable to
the first connector, wherein the
second circuit board is configured to move in a first direction along
the first circuit board to generally align the first and second
connectors;

18. A computer system comprising:
a first circuit board comprising a
first connector;
...a second circuit board coupled
to the housing, wherein the second circuit board comprises a second
connector; and
a biasing mechanism coupled to the housing, wherein the
biasing mechanism is configured to bias the second circuit board along a
curved path to connect the first and
second connectors in the second position of the module.

The Examiner rejected all independent claims as being anticipated by the same reference.

With regard to the "configured to move in a first direction" limitation, the Applicant argued in the Appeal Brief that the limitation was not present in the reference because "housing end 70 blocks the daughter board 8 from moving along the mother board at one end, and surface 34 of housing end 72 blocks the daughter board from moving along the mother board 14 at the other end." [See Fig. 2 below.]

In the Answer, the Examiner further explained the rejection as follows:

[P]lease note that the recitation that an element is "configure to" perform a function is not a positive limitation but only requires the ability to so perform. In this case, Grabbe discloses that the second circuit board (8) can move in a first direction along the first circuit board (14), as shown in the following figure. (Emphasis added. See Fig. 1 below.)

The Board noted that the Examiner did not point to an express teaching of the limitation, and therefore analyzed under an inherency theory:

[W]e note that the Examiner’s finding, portrayed in the figure on page 8 of the Answer that allegedly shows the daughter board moving in a direction along the mother board via a directional line added by the Examiner, is based on the mere possibility of such movement and thus is speculative and insufficient to establish the inherency of such movement. The Examiner does not provide any reasoning to support such a determination.

The Board therefore reversed the rejection of the claim (claim 9).

With regard to the "configured to bias the second circuit board along a
curved path" limitation,
the Applicant argued in the Appeal Brief that the limitation was not
present in the reference because:

the daughter board 8 is in contact with a ledge 68, it is impossible for the daughter board 8 to move along a curved path. See Grabbe Fig. 5. As such, the daughter board 8 moves laterally in a straight direction along the surface of the ledge 68 until the engaging surface 38 couples with the connector. [See Fig. 5 below.]

In the Answer, the Examiner further explained the rejection as follows:

[I]t is again noted that the recitation that an element is "configure to" perform a function is not a positive limitation but only requires the ability to so perform. In this case, the second connector (4) of Grabbe can rotate around a pivot structure and along a curved path, as shown in the following figure. (Emphasis added. See Fig. 3 below.)

Once again, since an express teaching was missing, the Board analyzed under an inherency theory, and found the Examiner's rejection to be in error:

In this regard, we note that the Examiner’s finding portrayed in the figure on page 10 of the Answer that allegedly shows the daughter board 8 moving in a curved path via a curved line added by the Examiner is mere speculation. The Examiner does not provide any reasoning to support a finding that Grabbe’s circuit board inherently moves in a curved path. (Emphasis added.)

My two cents: I don't view this case as being about inherency, at least not in the classic sense. The Examiner's position seems to be that there is no difference between "capable of" and "configured to". The parts in the reference were not designed to move in the claimed manner – but could move a micrometer or two if enough force was applied.

I have two objections to the Examiner's argument. First, even if the claims used the phrase "capable of", this is a strained interpretation of that phrase "capable of". It's akin to saying that one piece glued to another is "capable of being released" simply because the pieces come apart with a pry bar. Second, the claims didn't even use "capable of", they used "configured to." The Examiner's interpretation of "configured to" is simply unreasonable in my opinion.

It's been a long time since I saw a "creative" rejection like this. I wish the Board had hit the Examiner's argument head on rather than shoehorning it into an inherency framework.

Monday, November 8, 2010

Takeaway: The BPAI reversed an obviousness rejection because the benefit relied on by the Examiner as a motivation to combine (improved performance) was not related to the feature claimed, but was instead a benefit of another feature also taught by the reference. (Ex parte Keller.)

The claims on appeal related to a memory controller in a computer. Dependent claim 5 was rejected as obvious, and the feature argued by the Applicant related to selective interleaving: "wherein said method further comprises selectively only interleaving storage of consecutive memory chunks across said multiple sets of said physical dynamic memory devices within said first portion of said memory array,"

The Examiner rejected the parent independent claim using a combination of two references, and added a third reference (Roy) to reject dependent claim 5. As a motivation to combine Roy's interleaving technique with the other two references, the Examiner offered:

Roy teaches performance improvement techniques such as interleaving can reduce the memory system bus cycle time by up to half that of any of the DRAMs individually.

The Board first found that the combination did not disclose selective interleaving as described in claim 5. Roy disclosed the existence of two types of computer systems: those that interleave memory and those don't interleave memory. However, the Board found that this did not amount to a teaching of a system that selectively interleaved some chunks of memory while not interleaving other chunks of memory.

The Board went further to reject the Examiner's motivation to combine, finding that the teaching used by the Examiner as a motivation to add Roy to the combination did not relate to the feature used in the combination – selective interleaving. The benefit of reduced cycle time related instead to a different feature – increasing width of the data bus.

The Board found the Examiner's motivation to combine deficient in yet another way: solving the problem noted in the reference simply didn't suggest the claimed feature of selective interleaving:

Even if this disclosure related to the interleaving memory technique, recognizing problems with interleaving memory would not have taught or suggested combining interleaving and non-interleaving using a single memory array.

My two cents: The rationale used by the Examiner for the combination – improved performance – is an example of what I call a "generic rationale". This decision shows one of two ways I know to fight a generic rationale: argue that the Examiner hasn't shown that the combination
actually provides the benefit. The second is to argue that the alleged benefit isn't
really beneficial at all or is outweighed by drawbacks.

What initially drew my attention to this decision was the Examiner's mistake in relying on an advantage that wasn't related to the claimed feature. However, the Board's initial finding that the combination did not teach all the elements contained a useful nugget also.

Specifically, a reference that discloses the presence of a particular feature in one embodiment along with the absence of the same feature in another embodiment does not teach selectively enabling the feature. I've seen this sort of rejection before, and I'm glad to to see the Board is persuaded by this reasoning.

Related posts: Ex parte Khayrallah, which I discussed here,
makes the point that disclosure of two options for building a system is
not selective disablement of options during system operation. Ex parte Rykowski, which I discussed here, is another example of a successful attack on a generic rationale.

Sunday, November 7, 2010

A few weeks ago the Reexamination Alert blog ran a story (here) about a Tivo patent which survived an ex parte reexamination. (Details in PAIR, Reexam Control No. 90/009329). Though a great many reexams go to appeal, that wasn't needed here because the Examiner was persuaded by expert declarations filed in response to the final Office Action. The Reexamation Alert put it like this:

TiVo’s present success is the result of an interview with Examiners followed by two very powerful declarations. TiVo was represented at the interview by counsel, but also by TiVo
co-founder and ‘389 patent co-inventor Jim Barton, as well as UCLA
Professor John Villasenor. Barton’s declaration, and presumably his
presentation at the interview, established a critical nexus between the
substantial commercial success enjoyed by TiVo’s digital video recorder
and the “automatic flow control” required by claims 31 and 61. Dr.
Villasenor’s declaration detailed the technical distinctions between the
‘389 claims and the prior art, which he asserted “simply reacts to the
flow and does not control it.” Villasenor also argued that one skilled
in the art would have no reason to combine the references in the manner
proposed in the final rejection.

The use of expert declaration evidence is patent prosecution is a topic of particular interest to me, so I reviewed some of the file history, and in particular the declarations and responses which relied on this evidence. I've reviewed many Board decisions dealing with expert declarations, and in doing so have learned about some of the common problem areas with declarations. From what I can see, the expert declarations in this Tivo reexam skillfully handled several areas which Applicants often have trouble with.

Here's a few of the things that Tivo got right in its use of expert declarations -- along with the case authority for why I say each is "right":

Most importantly, Tivo used a declaration to explain technical facts, rather than simply putting this in a response as "mere attorney argument." In re Geisler, 116 F.3d 1465, 1470 (Fed. Cir. 1997)(attorney argument without factual evidence will not rebut prima facie obviousness).

The declaration includes credentials and those credentials are relevant to the art. For a discussion of the relevant case law, see my post here.

The declaration explains the relationship of the declarant to the assignee. Failure to do so can implicate inequitable conduct. An undisclosed business relationship between a
patent applicant and a declarant is material if "(1) the declarant's
views on the underlying issue are material and (2) the past relationship
is a significant one." Ferring B.V. v. Barr Labs, Inc., 437 F.3d 1181,
1188 (Fed. Cir. 2006).

The declaration itself gives facts and then draws technical conclusions, rather than conclusions unsupported by fact. The Board has broad discretion to accord little weight to declarations expressing an opinion as to fact when there is a lack of factual support for the opinions expressed. In re Am. Acad. of Sci. Tech. Ctr. , 367 F.3d 1359, 1368 (Fed. Cir. 2004).

In future posts I'll discuss some of these requirements in more detail. In the meantime, you can see a few posts which touch on expert declarations by selecting the label "1.132" in the list of Labels on the right-hand side of the blog.

Tuesday, November 2, 2010

Takeaway: In Ex parte Disney, the Board found that a swear-behind declaration did not show conception of a claimed spatial relationship because the claims used different terminology than the evidence. Specifically, the claims referred to the dimension as "vertical depth" and the inventor's notebook and invention disclosure form referred to the dimension as "long." Therefore, when differences in terminology exist between the evidence and the claims, you should also show that the terms are equivalent.

The technology in this application related to the structure of a transistor. The element at issue was:

first and second field plates disposed in the dielectric material of the first and second trenches, respectively, the first and second field plates having a first vertical depth ...
first and second gate members disposed in the dielectric material between the first and second sidewalls of the mesa, and the first and second field plates, respectively, the first and second gate members having a first vertical depth that is less than 20% of the first vertical depth.

Applicant submitted a declaration under § 1.131 to antedate the § 102 reference. The declaration attempted to establish conception before the effective filing date of the reference, coupled with diligence up to the time of filing of the application. The Applicant relied on a declaration from the attorney who prepared the application to establish diligence. The evidence submitted along with the inventor's declaration to establish conception included seven pages of notes and sketches from an inventor's notebook, a corporate invention disclosure form, and results from a computer simulation.

In the final Office Action, the Examiner alleged that the evidence did not show conception of the claimed depth relationship ("first and second field plates having a first vertical depth that is less than 20% of the first vertical depth"). Specifically, the Examiner alleged that:

"No teaching has been found in the Exhibits predating November 16, 2000, of said range. To the extent the Figures are of true scale, – and there is no statement on that either, the range appears not to be met by the figure illustrating the final structure, i.e., Figure 5K, in which the second vertical depth appears to be 25% instead of less than 20%."

The Appeal Brief argued against the Examiner's position by pointing to specific pages and figures in the three evidence documents and explaining how the claimed 20% range was described in these pages. After explaining the relevant portions of the evidence, the Appeal Brief concluded this argument as follows:

The evidence contained in the Declaration under 37 CFR 1.131 therefore clearly establishes the dimensional relationship recited in the relevant claims; namely, the vertical depth (i.e., length) of the gate members (3 pm) is less than 20% of the vertical depth of the field plate members (47 pm = Ld - TBox). Applicant respectfully submits that the range recited in claims 43-44 is fully supported in the Exhibits. Consequently, Baliga '372 should be removed from consideration as a prior art reference.

The Board did not discuss the showing of diligence, and instead moved directly to a discussion of whether the inventor declaration established conception of the claimed relationship between structures, namely, "first and second field plates having a first vertical depth that is less than 20% of the first vertical depth."

The Board found that the declaration was not sufficient. Where the Examiner took issue with the numeric ratio (less than 25% rather than less than 20%), the Board took issue with the terminology used to describe the dimensions. Specifically, the evidence referred to a vertical trench that was 3 um long, where the claim referred to the depth of the plates in the trench. The Board explained that:

The Rule 131 declaration submitted by Appellant to antedate the November filing date of the Baliga ‘372 reference clearly shows a gate poly and a field plate poly, but does not show a depth of the gate members that is less than 20% of another vertical depth (FF4, referring to the figure below showing a gate poly and a field plate poly, and the explanation “Added Vertical (trench) Gate 3μm Long; with Pbody 2.5 μm long, N+ Source 0.2 μm long”).

A measurement that is “long” is not an indication of depth (FF 4). Accordingly, we find that Appellant’s declaration does not prove that he invented the claimed vertical depths prior to the date of the reference to Baliga ‘372.

My two cents: When was the last time you wrote claims and didn't change the terms used by the inventor? That's a large part of what we patent attorneys/agents get paid for ... picking the right words. So I gotta believe this mismatch in terminology will be a common occurrence when you submit inventor-provided evidence with a swear-behind declaration.

The lesson here is not to ignore the discrepancy. Instead, you should explain it. It seems to me that dimensions in particular are easy to explain: depending on what your perspective is, length could also be considered width or depth.

From what I've seen, your best chance is to include the explanation of the discrepancy in the inventor declaration. You can try putting it in as a argument, and you might convince the Examiner that way. But if you go that route on appeal, you risk the Board ignoring your arguments because "[a]rgument of counsel cannot take the place of evidence lacking in the record" (Meitzner v. Mindick, 549 F.2d 775, 782 (CCPA 1977)).

I also find it significant that the Board did not question the sufficiency of the showing of diligence. I've seen plenty of Board decisions that didn't reach the merits of whether the evidence showed conception / reduction because diligence was lacking. Therefore, I infer that there was nothing obviously wrong with the diligence showing. Furthermore, neither the Examiner nor the Board questioned the sufficiency of the evidence in showing any of the other claim limitations – only the 20% limitation seemed to be an issue.

It's true that the Board found that this evidence had a hole in it, and you should take note of this. Nonetheless, I think this swear-behind was still a pretty good showing overall. Consider adding this application to your list of example swear-behind declarations – it's available in PAIR.

Disclaimer

Disclaimer: The opinions expressed on this Blog/Web Site ("Blog") are those of the author and do not represent the views of her law firm, colleagues, or clients. The Blog is not legal advice and is offered for educational purposes only. The Blog does not create any attorney-client relationship. Comments posted on the Blog are not treated as confidential; therefore, do not post sensitive information