[00:00:01] Speaker 04: Our final case for argument is 25-1302, iCharts versus Tableau Software. [00:00:11] Speaker 00: May it please the court, my name is Will Hubbard and I'm here on behalf of iCharts. [00:00:15] Speaker 00: I'd like to start by briefly highlighting a few key features of the technology in these certified patents. [00:00:21] Speaker 00: The patents claim systems and methods for generating and sharing charts that are both interactive and self-contained. [00:00:29] Speaker 00: A chart is interactive when it can receive user input and then re-render or update its display using that input as a parameter. [00:00:38] Speaker 00: A chart is self-contained when the chart can re-render itself without relying on the system that created the chart in the first place. In other words, the chart updates locally without the involvement of its generation software. [00:00:53] Speaker 00: As iCharts explained to the complaint, the re-rendering is performed client-side rather than server-side. And that's Joint Appendix 1332, paragraphs 26 and 36. [00:01:04] Speaker 00: Importantly, the assertive patents do not simply claim interactive charts or self-contained interactive charts. Rather, the patents claim platforms that combine chart templates with data to produce self-contained interactive charts and then share them without losing those features. [00:01:25] Speaker 00: Turning to Alice Step 1, while there is no definitive test for determining whether a patent is directed to an abstract idea, this court has noted that a key consideration is whether a patent claims an improvement to computer technologies. [00:01:40] Speaker 00: Here, there is really no dispute that the patents claim such improvements. [00:01:45] Speaker 00: Plainly, the patents relate to computer technologies. The district court agreed. describing the asserted patents as being directed towards generating and sharing self-contained interactive charts on computers. [00:02:00] Speaker 00: This concept of generating and sharing self-contained interactive charts is inherently computer-based, given that a chart is interactive when it re-renders itself based on user input, and a chart is self-contained when that change comes from code that is run locally. [00:02:16] Speaker 02: What's the... [00:02:17] Speaker 02: Computer technology. It's software, right? [00:02:21] Speaker 00: That's correct, Your Honor. [00:02:22] Speaker 02: It's passing information. [00:02:26] Speaker 00: That's correct, Your Honor. But this court has made clear in cases like DDR and Infish that software technologies can provide the benefits that indicate that a patent is not directed to an abstract idea. [00:02:40] Speaker 04: But in cases like that, it was because it improves the functioning of the computer as a whole. [00:02:46] Speaker 04: For example, reduced memory or expedited processing power or something along those lines. So it was software, the end result of which was not just to better automate the software program that the user was seeking, but rather to improve the functioning of the computer. So how does this do that? [00:03:07] Speaker 00: Yes, Your Honor. There are three respects in which the claimed invention improves the operation of the computer system, the networked computer system. [00:03:16] Speaker 00: The first is that chart interactivity being conducted client-side allows for re-rendering without repeated calls to a distant server and without the need for special software on the user's computer, thereby improving data security and scalability. [00:03:33] Speaker 00: Second, unlike some interactive charts, the interactive charts produced by the patented platforms are portable. They can be copied from one environment to another while retaining their interactive quality. [00:03:43] Speaker 00: And then third, The Clayton invention automated it. [00:03:47] Speaker 04: I certainly don't see how the second one has anything to do with improving a computer. It improves the utilization of the chart by the user, but it doesn't improve the computer or the network. [00:03:57] Speaker 00: So it improves the ability to share interactive charts in a networked environment. [00:04:03] Speaker 04: That's exactly right. That's like... An improvement to Excel makes spreadsheets more readily usable by the user. That's not an improvement of the computer. That's an improvement of the software-using experience. [00:04:19] Speaker 04: And that's not what we've ever said amounts to a technological improvement in these kinds of software cases. [00:04:25] Speaker 00: So I understand the distinction that you're making, and I agree that that distinction is a meaningful one in the sense that the charts don't make the network run faster, but by making the charts self-contained, you improve the scalability so that you can use charts in the networked environment without overloading the networked environment. Similar concerns came up, for example, in this court's BASCOM decision. In that case, as you recall, it was an issue of filtering technologies where the innovation was shifting filtering to the server rather than being run individually on the user's computer. [00:05:03] Speaker 00: And there the court said that shifting that processing to the server did provide a technological improvement because it supported scalability. [00:05:12] Speaker 02: Where does the claim describe how to achieve re-rendering, which apparently is key here? [00:05:20] Speaker 00: So the claims do not describe re-rendering. Our position is that that is a term that would be understood by a person of ordinary skill in the art based on the specification. But the claim itself does not describe the process of re-rendering. [00:05:35] Speaker 00: So I'd like to turn to the second consideration. [00:05:37] Speaker 03: It seems to me that what the claims do is that they're claiming a result. [00:05:43] Speaker 03: And there's nothing there that I see that tells me either how to get there or that the claim itself is directed to that result. [00:05:53] Speaker 00: Yes, Your Honor. So we disagree with the premise that the claims do not describe how to get to the result. And in particular, the claims describe a four-part architecture involving the collection of data, either by uploading or by selecting a data feed, the combination with a chart template, the generation of the interactive chart, and then the sharing of the interactive chart in a fashion that preserves those qualities. The patents then also describe a three-part process for interactivity where the chart is rendered. [00:06:27] Speaker 00: It is then accepting a user input from the local user, using that input as a parameter to then re-render. So as an initial matter, we believe that that does provide sufficient detail, the how that you were asking about. How does the invention perform this feature? [00:06:46] Speaker 04: How? The claim doesn't tell you how... the interactivity allows for the re-rendering. It doesn't explain anything. [00:06:55] Speaker 00: So the claims themselves do not describe that. We agree. We agree. And the specification doesn't describe it in detail, but the specification does do two important things. The specification provides examples of working embodiments. Those examples are the screenshots that run for many pages, the figures at the beginning of all three patents, the screenshots from iChart's working embodiment of the invention. Moreover, as the court noted in Enfish, much of the advancement made in computer technology consists of improvements that, by their very nature, may not be defined by particular physical features, but rather the logical structures and processes. [00:07:38] Speaker 00: That is what we submit the patent provides, that provides the logical structures and processes, and the more fine-grained details that you are asking about, that was left to the ordinary skill of the ARP. [00:07:51] Speaker 00: So there's these three considerations that the court has identified in trying to determine if a patent is directed to an abstract idea. One is this issue, and I understand that you've got some concerns about it, with the technological improvement. Another is this question about functionality. But there's a third consideration as well, and that's whether or not the patents target some long-practice, real-world activity and simply says, do it on a computer. And here the district court said that that was the case, And we disagree. [00:08:23] Speaker 00: And that's because the district court didn't just strip generic computer aspects from the claims. Rather, the district court overgeneralized the claims. [00:08:34] Speaker 00: Fundamentally, the district court conflated interacting with a chart with a chart being interactive. The comparison that the district court made was to a printed map of a printed map that could then be shared and then interacted with by folding. But that is interacting with a static map. That is not a chart that is re-rendered or recreated based on a user input. Under the district court's view, for example, a chart would be re-rendered simply by moving closer to the chart because you are interacting with the chart. [00:09:12] Speaker 00: The fundamental problem is that this self-contained interactive chart does not exist outside of the computing environment. [00:09:20] Speaker 00: This court is warned against such overgeneralizations at step one, for example, in Data Engine versus Google, saying that it is not enough to merely trace the invention to some real-world analogy. [00:09:32] Speaker 00: I'd like to turn to the second step of the Alice analysis. [00:09:42] Speaker 00: This step, as you know, evaluates whether the claims involve more than a combination of the abstract idea with conventional, routine, and well-understood features. As a result, to the extent claim features are not considered in step one, they should be considered in step two. [00:10:01] Speaker 00: Courts must evaluate both whether individual claims as well as the ordered combination of those elements is conventional. And as you know very well, this often raises factual questions under the Atrix decision. So the district court found that the combination of elements was conventional because it involved only a combination of the abstract idea, routine applications of Flash, and prior art uses of Google Spreadsheets. [00:10:34] Speaker 00: This court emphasized in BASCOM that ALICE Step 2 requires more than just this individual element analysis, but rather some factual support as to why the combination would be conventional. Unfortunately, the district court engaged in the kind of ex-post-hindsight bias approach that plays the obviousness analysis, using the patent itself to describe the combination of elements and then declaring it to be conventional. even though iCharts alleged in its complaint that this combination was unconventional, even though iCharts alleged in its complaint that the claimed platform provides substantial benefits over the prior art. [00:11:22] Speaker 00: In fact, far from conceding that the combination of Flash and of flashing Google Spreadsheets was somehow conventional, the assertive patents highlight the shortcomings of Google Spreadsheets insofar as it cannot support self-contained interactive charts, and as a result requires repeated calls to a distant server, increasing network traffic. [00:11:45] Speaker 00: Now, I want to also highlight the court statements regarding Flash, Adobe Flash. The court said that the combination of elements was conventional because Adobe Flash was a conventional tool, conventionally applied. There's no factual support whatsoever that this combination was conventional. [00:12:09] Speaker 00: And... [00:12:12] Speaker 00: And in doing so, the court made an unsupported, incorrect factual finding at the pleading stage. [00:12:19] Speaker 00: Even worse, the district court improperly ignored contrary allegations regarding the use of Flash. iCharts alleged in its complaint that its own system was not created entirely using Flash. Rather, there are additional programming languages involved in creating other components, including programming in Java. [00:12:41] Speaker 04: During your rebuttal time, do you wish to say that? [00:12:44] Speaker 00: Yes, Your Honor. Thank you. [00:12:55] Speaker 01: May it please the court, Ryan Tize on behalf of Tableau. Good morning, Your Honors. [00:13:00] Speaker 01: First, I'm just going to jump right into your questions as opposed to opposing counsel. The first, you're right. All these claims do is pass information, obtain information, store information, and display information. Historically, through this court's precedence, that's an abstract idea. Nothing to the next question is how does it improve computer technology? There is no improvement to computer technology here. The alleged client-side rendering is nowhere found in the claims. And if you look at the claims, the representative claims, one claims talks about showing charts on websites. [00:13:35] Speaker 01: So obviously the website is not on the client device. You go to the website and it re-renders on that device. That's not client-side re-rendering. [00:13:45] Speaker 01: What do the patents claim? You're right, Judge Reyna, is functional results. And that is the greatest indicator of an abstract idea. It doesn't explain how to achieve anything. It merely says enabled, configured to all results-oriented claims. [00:14:03] Speaker 01: So what the service patents are trying to get at is whether iCharts can patent the idea of packaging a chart in a format that can be carried to other websites and retain interactivity, all using conventional technology. Again, they never explain how to achieve that interactivity or the self-contained. It just says that is the goal. [00:14:30] Speaker 01: And the district court properly found all results oriented and searched over and over again for the how and even asked for supplemental briefing about how the particular element of the claim, that patentee or plaintiff. [00:14:46] Speaker 03: There's a lack of specificity in the claims. [00:14:50] Speaker 01: 100% on how to achieve anything. It is aspirational, goal-oriented. [00:14:57] Speaker 03: Which may be true, but what does a claim have to say in order to lend more specificity? [00:15:06] Speaker 01: I think a good example would be the Contour IP case, in which there was a specific improvement to the technology. And in that case, it was simultaneously creating a high and low version of a video, sending the low version to the remote device to enable the user to control. [00:15:29] Speaker 03: How do you distinguish this between APHIS and Datto? [00:15:34] Speaker 01: I think in all those cases, there's a clear demarcation. Is there an improvement to the computer technology or what you're trying to build? Here, there's no improvement in the claims, and you're required to look at the claims. In each of those other cases where this court has found patent eligibility, there is an improvement to the claims. The contour IP holdings, the improvement to how – Excel works, where you place a filter. [00:16:03] Speaker 03: Section 101 is envisioned and was supposed to be, and I guess still is supposed to be, a low threshold. [00:16:12] Speaker 03: And your argument about specificity concerns me in that aren't we reaching into Section 112? [00:16:20] Speaker 01: I think Section 112 is separate, and as a district court noted, it may have Section 112 problems, but as a threshold matter is, is the claim directed to an abstract idea? And without the specificity, and more, it's less about the specificity, but more about claiming results, right? That is not an invention. It is an aspiration. And there has to be something in the claim that is the improvement. And opposing counsel could not point to anything in the claim that is the improvement. [00:16:52] Speaker 01: And if you go back to the hearing at the district court, the same question was posed. And the counsel at the district court level for I-CHART's went through the claims and said everything was conventional or results-oriented except for one element, and that's the self-contained interactive chart. But nowhere in the claims does it say how do you create the self-contained, what makes it interactive, and how is that retained? That is nowhere in the claims. So again, it's aspirational, and that's important. [00:17:23] Speaker 01: And so this is an abstract information. [00:17:26] Speaker 03: Isn't the self-contained nature of the interactive device an improvement? [00:17:33] Speaker 01: Well, it asks, you know, what does self-contained mean? They point to Flash as achieving the self-contained component. [00:17:44] Speaker 01: Excuse me? [00:17:45] Speaker 03: When they say self-contained, aren't we... Are we now entering into the area specificity? [00:17:51] Speaker 01: I don't believe so. I think it's still result-oriented. [00:17:56] Speaker 01: How do you achieve the self-contained is the question. The claims don't answer that question. [00:18:01] Speaker 01: So what's the invention? [00:18:03] Speaker 01: Just having a self-contained chart? [00:18:05] Speaker 03: Yes, an abstract idea. Here all the claims do is receive, share, and display data. [00:18:16] Speaker 01: And that is historically, with this court's precedent, is an abstract idea. And nothing in these claims is any different. I think GoTV from 2026 is a great example of why the claims here don't pass the eligibility requirement. And if you look at those claims, again, all results-oriented claims. and did not provide a solution in the claims and nothing in the specification either. And I-Charts admitted there's nothing in the claims that identified the technical improvement. [00:18:50] Speaker 01: And your job is to look at the claims. Is there an improvement? [00:18:58] Speaker 01: So, not unless you have any other questions, I would submit on this record. [00:19:14] Speaker 00: Thank you, Your Honor. I think that I've heard a new abstract idea opposed by my friend on the other side. The functionality concerns do not relieve the patent challenger of the obligation to follow the analysis prescribed in ALICE. There must be an abstract idea identified. And secondly, we consider whether additional features rendering it an inventive concept. [00:19:40] Speaker 00: My friend on the other side said that the idea was to receive, share, and display data. That changes the analysis dramatically from what the district court said. That's a very different idea. Now, the reason that is important, because if you make that change, the particular features of the invention that previously were considered at step one now need to be considered at step two. And doing so puts this case on all fours with this court's BASCOM decision. [00:20:22] Speaker 00: All right, in the BASCOM decision, the prior art described user customizable filtering of internet content on local computers. The patents in that case claimed a system that shifted this filtering to a shared server And this court found that to be an unconventional change. Similarly here, if the idea at step one is framed at a very high level of abstraction as just manipulating data, all of the features of the claimed invention regarding the self-contained interactive nature must be considered at step two. [00:20:52] Speaker 00: And as in BASCOM, we have shifted where in the networked environment the processing occurs. In BASCOM, it was shifted from the local user computer to the server. In this case, we are shifting it from the server to the local user. [00:21:06] Speaker 04: What about the point that actually the chart is on the website, which is clearly not shifted to the local user? [00:21:12] Speaker 00: So it is processed locally. So when the website loads on the user's computer, the self-contained chart is pulled at that moment, and then interaction is run locally at that point without being a call to a remote server every time. [00:21:26] Speaker 04: Why do you have to call the remote server to get it pulled? [00:21:29] Speaker 00: Initially once, but then thereafter, each interacted. In contrast, with Google Spreadsheets, every time you move your mouse to interact, Google Spreadsheets would be sending you an updated picture and an updated picture and an updated picture. [00:21:41] Speaker 00: Thank you very much. [00:21:42] Speaker 04: Thank you so much.