Dissenting opinion filed by Circuit Judge MAYER.
PLAGER, Circuit Judge.
This is a patent infringement case in which plaintiffs, MySpace, Inc. and craigslist, Inc., filed declaratory judgment suits in the Northern District of California against defendant GraphOn Corporation (“GraphOn”). Plaintiffs alleged that certain patents owned by GraphOn were invalid and not infringed by them. GraphOn counter-claimed for infringement, and asserted third-party claims against Fox Audience Network, Inc. (“FOX”). Plaintiffs’ suits were consolidated. Shortly thereafter, FOX joined MySpace in a summary judgment motion on the issue of invalidity, and craigslist followed with its own summary judgment motion that incorporated by reference the MySpace/FOX motion. These three parties will hereafter be referred to as “the MySpace parties.”
The District Court granted the MySpace parties’ motion for summary judgment, and rendered final judgment for the MySpace parties. GraphOn timely appeals. Because we believe the case is properly decided under §§ 102 and 103 of the Patent Act and not under § 101, and because the district court did not err in its grant of summary judgment of invalidity of the patents-in-suit under those sections, we affirm.
Background
1. Underlying Technology
For purposes of this opinion, we need only summarize the history and development of the underlying patented technology in this case, which relates to the ability to create, modify, and store database records over a computer network. For a full description, see the district court’s opinion, MySpace, Inc. v. Graphon Corp., 756 F.Supp.2d 1218 (N.D.Cal.2010).
In the early 1980’s, desktop software applications ran entirely on a single computer, so that the files, code, and data relating to a given program were all stored on a personal computer (“PC”). This configuration presented a problem for larger-scale applications. Users could not easily share documents, images, files, and other • data between computers.
The mid-1980’s to mid-1990’s brought about the development of client-server applications. Id. at 1222. Companies began placing their applications on a server so that client machines could access files, documents, and other data held in a centralized location. This configuration allowed for easier sharing of information and enabled users to reduce the amount of data stored in the memory of their PCs. The data stored on the centralized servers were generally stored in file systems. Id. File systems are a method of organizing and storing data that are typically configured hierarchically using a parent-child type of relationship1 similar to the folder [1254]*1254and directory configuration common in today’s PC operating systems.
While a marked improvement from the early single desktop PC configuration, the file system-based client-server configuration was not without its problems. Issues such as functionality, performance, and data security became troublesome for many applications. Spielman Deck at ¶ 36. Further, the file system method of data storage was not easily searchable or writable. Id. at ¶¶ 41 and 69-70. Consequently, the notion of using a relational database to store information on these servers was born.
A relational database separates the stored data into multiple relations or “tables” and connects them through the use of identification (“ID”) fields. MySpace, Inc., 756 F.Supp.2d at 1223. An ID field generally is a numeric field that can be synchronized across multiple tables in order to allow for faster searching, storing, and editing of information. Because the data is compartmentalized into tables, relational databases can be configured so that the ID fields that map to sensitive textual fields, such as security numbers and bank account information, can be locked while less guarded data, such as a person’s name and gender, are available upon query.
2. Patents-In-Suit and Procedural History
The four patents at issue, U.S. Patent Nos. 6,324,538 (“'538 Patent”), 6,850,940 (“'940 Patent”), 7,028,034 (“'034 Patent”), and 7,269,591 (“'591 Patent”), disclose a method and apparatus that allow a user to create, modify, and search for a database record over a computer network. Id. All four patents claim priority to a parent application, filed on December 14, 1995, and subsequently issued as U.S. Patent No. 5,778,367 (“'367 Patent”), that is not being contested in this case. Id.
The inventors of the patents-in-suit were motivated to find a way to better control the content of an Internet listing. Id. Early search engine developers edited and categorized each listing based on their own understanding of the listing without input from the user. Id. This occasionally created listings that were miscategorized or that contained typographical errors — both of which were difficult to search. The inventors attempted to solve these problems by creating a system that enabled a user to control the creation and classification of the user’s own database entry over a computer network such as the Internet. Id. Users could create a database entry with their own text and graphics and then choose or create searchable categories that best matched the information. Id. The patents-in-suit claim various aspects of this invention.
Before the earliest priority date of the patents-in-suit, however, the Mother of all Bulletin Boards (“MBB”) was developed by Dr. Oliver McBryan at the University of Colorado. The MBB was first made available for public use in November 1993, more than two years before the priority application for the patents-at-issue was filed. Id. at 1224. The MBB provided the ability to have online Internet catalogues that could grow through user input without the need for intervention by a webmaster or administrator. Id. The MBB stored all its entries in the file system of the computer running the MBB. The data within the file system was stored hierarchically as opposed to relationally.
As earlier noted, not long after the MySpace and craigslist cases were consolidated in May of 2010, MySpace and FOX [1255]*1255jointly filed a motion for summary judgment on the issue of invalidity of all four patents-in-suit. This motion was based on the MBB prior art system. The motion sought summary judgment that all the claims were invalid as anticipated or obvious. And as noted, days later craigslist also filed a similar motion for summary judgment. A hearing was held on October 1, 2010. Following the hearing, and pursuant to the court’s instruction, each party filed supplemental briefs directed towards specific topics including the functioning of the MBB software. In November 2010 the district court entered an order granting the motion for summary judgment of invalidity. The district court concluded that all the claims were either anticipated or rendered obvious by the MBB, and entered a final Judgment under Fed. R. Civ. Pro. 54(b) for the MySpace parties.
GraphOn timely appealed. Under 28 U.S.C. § 1295(a)(1), we have jurisdiction over final judgments arising under the patent laws.
Discussion
1. Claim Construction
The parties dispute what is covered by the term “database,” a term that is found in each of the 73 claims in the patents-in-suit. Although our precedent establishes that claim construction is an issue of law that we review without deference, Cybor Corp. v. FAS Techs., Inc., 138 F.3d 1448, 1454-55 (Fed.Cir.1998) (en banc), we weigh carefully the guidance provided by the trial court.
If the term “database” is understood to cover different types of data organization systems, including both file (hierarchical) and relational systems, then the MBB, which all parties concede is prior art and which taught the same basic approach as the patents-in-suit, would invalidate all the claims as either anticipated under 35 U.S.C. § 102 or obvious under § 103. If, on the other hand, “database” covers only relational systems as urged by GraphOn, it would not be so clear that the MBB invalidates the claims because the patents-in-suit would be understood to disclose and claim a differently-designed system to accomplish essentially the same end. At a minimum there would be a genuine issue of disputed fact on the question of invalidity, and summary judgment would be inappropriate.
The district court construed “database” to mean “a collection of data with a given structure that can be stored and retrieved,” thus including both file (hierarchical) and relational systems. MySpace, Inc., 756 F.Supp.2d at 1232. This was essentially the construction urged by the MySpace parties. GraphOn argues that we should reverse the district court’s “database” construction and redefine it as limited to a relational database. In GraphOn’s view, the claims, written description, and file histories limit, the term to relational databases. Thus, according to GraphOn, hierarchical databases, such as the file system used by the MBB, cannot be prior art.
In construing the claims, we begin with an examination of the ordinary and customary meaning of the claim language itself in the context of the written description of the invention found in the patent, and the prosecution history. Phillips v. AWH Corp., 415 F.3d 1303, 1312-13 (Fed.Cir.2005) (en banc); Medrad, Inc. v. MRI Devices Corp., 401 F.3d 1313, 1319 (Fed.Cir.2005). Indeed, we have deemed the written description the “best source” for understanding the technical meaning of a claim term. Phillips, 415 F.3d at 1315. But limitations from parts of the written description, such as the details of the preferred embodiment, cannot be read into the claims absent a clear intention by the patentee to do so. Teleflex, Inc. v. Ficosa [1256]*1256North Am. Corp., 299 F.3d 1313, 1326 (Fed.Cir.2002).
It has been suggested that a reading of this court’s claim construction cases indicates that outcomes depend on the judges’ predilection for one of two approaches.2 One approach is to focus on the invention disclosed in the patent: “[t]ry to understand what the inventor has invented (what he says is his contribution in the art) and then choose the claim meaning that best fits the invention.”3 The other is to focus on the words that the prosecuting lawyer used to craft the claims and “then apply legal rules of construction to divine the meaning of the claim.”4 While this is insightful regarding the approaches highlighted in one or another of our cases, it is an over-simplification to suggest that these are competing theories; rather, they are complementary. An inventor is entitled to claim in a patent what he has invented, but no more.5 He can, however, claim less, to avoid prior art or for any other reason. Therefore, in construing a claim there are two limiting factors — what was invented, and what exactly was claimed. To determine the former — what was invented — we look at the entire patent, with particular attention to the specification (the written description of the invention and the several claims made). To determine the latter— what exactly was claimed — the focus is on the precise words of the particular claim or claims at issue; the written description and preferred embodiments are aids in understanding those words. In the case before us, proper claim construction requires that we understand what the invention encompasses as well as how the claims are stated.
The “Summary of the Invention” section of the written description for all four of the patents-in-suit broadly describes the database as being a collection of user entries that “are automatically collected, classified and stored ... in a searchable and retrievable form.” '538 Patent col.3 ll.2-3. All types of databases — relational, hierarchical, or otherwise — are searchable and retrievable. Thus, nothing in this language serves to limit the invention to a relational database.
Further, the “Background of the Invention” section discusses the limitations of prior art systems in placing “databases of various kinds” directly on the web, and suggests that the disclosed invention overcomes those disadvantages. See, e.g., '538 Patent col.l 1.37 and col.2 ll.57-58. Taken together, this language indicates that the general term “database” in the claims can encompass any of the “various kinds” of databases known in the art at that time.
GraphOn argues that the “various kinds” modifier used in the written description was meant to refer to various kinds of relational databases as opposed to the structure of the database itself. We agree with the district court that this argument is not supported by the context. For example, the “Detailed Description of the Preferred Embodiments” section discusses a type of search called a “category search” in which the “[cjategories are represented in computer memory in the form of a tree structure ... [in which] the user can click on any category to go to the next level, and can click on any entry to bring up the mini page of the entry.” '538 Patent col. 11 ll.1-7. Such “tree structure” termi[1257]*1257nology is more consistent with the organizational structure of a hierarchical database rather than a relational database.
While this preferred embodiment does not itself limit the claims, it does suggest that the inventors intended that the invention encompass various database features, including those of hierarchical databases. See Helmsderfer v. Bobrick Washroom Equip., Inc., 527 F.3d 1379, 1383 (Fed.Cir. 2008) (“Our case law generally counsels against interpreting a claim term in a way that excludes the preferred embodiment from the scope of the invention.”). Because the preferred embodiments describe features contained in multiple types of databases6 and the written description is devoid of a clear indication that the invention should be limited to one particular type of database, it would be improper to limit the construction to relational databases.
Thus we conclude that the district court’s claim construction of “database” is both reasonable and supported by the context.
2. Invalidity Under §§ 102 and 103
The district court held all the claims at issue invalid under a combination of sections 102 and 103 of the Patent Act. We review a district court’s grant of summary judgment of invalidity without deference, drawing all reasonable inferences in favor of the non-movant and reapplying the standards used by the district court. Slip Track Sys., Inc. v. Metal-Lite, Inc., 304 F.3d 1256, 1262 (Fed.Cir.2002). When, as here, the facts underlying an invalidity determination are not in dispute, we determine “whether summary judgment of invalidity is correct by applying the law to the undisputed facts.” Tokai Corp. v. Easton Enters., Inc., 632 F.3d 1358, 1366 (Fed.Cir.2011).
Even given the district court’s construction of the term “database,” GraphOn argues that the district court erred in its conclusion that all the claims were either invalid as being anticipated under 35 U.S.C. § 102 or obvious under 35 U.S.C. § 103. GraphOn argues that the court merely analyzed the claims on a limitation-by-limitation basis rather than discussing the claim language as a whole. It is certainly true that section 102 speaks in terms of “the invention” having been in public use more than one year prior to the date of the application for patent, and that section 103 requires that the subject matter “as a whole” would have been obvious at the time the invention was made. See 35 U.S.C. §§ 102(b), 103(a). Thus, ordinarily we would expect the district court to conduct a complete assessment of the claim language. Trial courts analyzing claim limitations should strive to connect those limitations to the context of the claim as a whole when making summary judgment determinations regarding validity. Such a step may seem a bit pro forma to some, but as the statute and our cases make clear, patent claims are not judged solely by their individual limitations.7
Even so, such a discussion is not necessarily a prerequisite to the grant of summary judgment. In a case such as this, in which all the claims share a common term that lies at the heart of the invention, we conclude that the district court’s analysis of the “database” term adequately sup[1258]*1258ports the court’s assessment that there is no triable issue of fact as to whether the MBB is a database as used in the claims. Thus we find no error in the trial court’s overall conclusion that the claims are anticipated or obvious.
3. Invalidity Under § 101
The dissent proposes that this appeal should be decided under § 101 of the Patent Act, the section that describes what inventions are eligible for patenting, rather than, as we have done, under §§ 102 and 103, anticipation and obviousness. The dissent considers the subject matter eligibility requirements contained in § 101 to be an “antecedent question” that must be addressed before the court can reach the §§ 102 and 103 issues. Op. at 1264. That position is not unique to the dissent; one can find support for it, as the dissent notes, in the literature and in the language found in some cases.8 Other voices, however, urge judicial restraint in the face of what has become a plethora of opinions adding to our § 101 jurisprudence.9
At issue here was the validity of four patents, with all four patents addressing the same general subject matter. The trial court had before it several summary judgment motions challenging the validity of the patents under §§ 102 and 103 of the Patent Act. The trial court decided the case under those sections, finding the patents invalid, and that is the judgment now on appeal. Nevertheless, the dissent argues forcefully that we should not, indeed we cannot, reach those issues until we first address the § 101 question, stating that “[a] robust application of section 101 is required to ensure that the patent laws comport with their constitutionally-defined objective.” Op. at 1269. In the dissent’s view, the patents in this case fall well short of the requirements under § 101 for patentable subject matter and thus are invalid, agreeing with the trial judge (and with us), but getting there through a different jurisprudential path.
Even assuming we could reach out for the § 101 issue without having it raised by the parties or decided by the trial court, there is an even more basic problem with the dissent’s position. The problem with addressing § 101 initially every time it is presented as a defense is that the answer in each case requires the search for a universal truth: in the broad sweep of modern innovative technologies, does this invention fall outside the breadth of human endeavor that possibly can be patented under § 101?
The Supreme Court recognizes that Congress intended in this general provision that the patent laws should be given wide scope. Diamond v. Chakrabarty, 447 U.S. 303, 308, 100 S.Ct. 2204, 65 L.Ed.2d 144 (1980). However, the Court has established, again in broad terms, three areas of activity that are excepted. These exceptions, according to the Court, are “laws of nature, physical phenomena, and abstract ideas.” Bilski v. Kappos, — U.S. -, [1259]*1259130 S.Ct. 3218, 3225, 177 L.Ed.2d 792 (2010) (citing Chakrabarty, 447 U.S. at 309, 100 S.Ct. 2204). Over the years courts have found dealing with “laws of nature” and “physical phenomena” reasonably manageable. Though hardly bright-line,10 the standards that have emerged from the cases addressing these exceptions provide workable guidance.11
When it comes to explaining what is to be understood by “abstract ideas” in terms that are something less than abstract, courts have been less successful.12 The effort has become particularly problematic in recent times when applied to that class of claimed inventions loosely described as business method patents. If indeterminacy of the law governing patents was a problem in the past,13 it surely is becoming an even greater problem now, as the current cases attest.
In an attempt to explain what an abstract idea is (or is not) we tried the “machine or transformation” formula — the Supreme Court was not impressed. Bilski, 130 S.Ct. at 3226-27. We have since acknowledged that the concept lacks of a concrete definition: “this court also will not presume to define ‘abstract’ beyond the recognition that this disqualifying characteristic should exhibit itself so manifestly as to override the broad statutory categories of eligible subject matter....” Research Corp. Techs., Inc. v. Microsoft Corp., 627 F.3d 859, 868 (Fed.Cir.2010).
Our opinions spend page after page revisiting our cases and those of the Supreme Court, and still we continue to disagree vigorously over what is or is not patentable subject matter. See, e.g., Dealertrack, Inc. v. Huber, 674 F.3d 1315 (Fed. Cir.2012) (Plager, J., dissenting-in-part); Classen Immunotherapies, Inc. v. Biogen IDEC, 659 F.3d 1057 (Fed.Cir.2011) (Moore, J., dissenting); Ass’n for Molecular Pathology, 653 F.3d 1329 (Fed.Cir. 2011) (concurring opinion by Moore, J., dissenting opinion by Bryson, J.); see also In re Ferguson, 558 F.3d 1359 (Fed.Cir. 2009) (Newman, J., concurring).
This effort to descriptively cabin § 101 jurisprudence is reminiscent of the oenologists trying to describe a new wine. They have an abundance of adjectives — earthy, fruity, grassy, nutty, tart, woody, to name just a few14 — but picking and choosing in a given circumstance which ones apply and in what combination depends less on the assumed content of the words than on the taste of the tongue pronouncing them.
Beyond railing at the problem, there is the alternative that Congress has provided — a clear path for courts in deciding the question of patent validity. In section 282 of the Patent Act, Congress created a presumption of validity for an issued patent, and then specified the “defenses in any action involving the validity ... of a patent.” These are “any ground specified in part II of this title as a condition of pat[1260]*1260entability ” (emphasis added), and “failure to comply with any requirement of sections 112 or 251 of this title.”15 The two sections of part II that Congress has denominated as “conditions of patentability” are § 102 (“novelty and loss of right to patent”) and § 103 (“nonobvious subject matter”).
In each of sections 102, 103, and 112, the validity issue turns on whether one or more of the particular claims in the patent are rendered invalid by the specific criteria of the statutory section as applied to that claim. These criteria are well developed and generally well understood.16 In most cases when properly applied they will address the specifics of the case and decide that particular case, nothing more. No universal truths need be found that are necessarily applicable to the scope of patents generally, and in deciding the case the corpus of jurisprudence need not be expanded, contracted, redefined, or worse, become the source of yet more abstractions.
Rather than taking the path the dissent urges, courts could avoid the swamp of verbiage that is § 101 by exercising their inherent power to control the processes of litigation, Chambers v. NASCO, Inc., 501 U.S. 32, 43, 111 S.Ct. 2123, 115 L.Ed.2d 27 (1991), and insist that litigants initially address patent invalidity issues in terms of the conditions of patentability defenses as the statute provides, specifically §§ 102, 103, and 112. If that were done in the typical patent case, litigation over the question of validity of the patent would be concluded under these provisions, and it would be unnecessary to enter the murky morass that is § 101 jurisprudence. This would make patent litigation more efficient, conserve judicial resources, and bring a degree of certainty to the interests of both patentees and their competitors in the marketplace.
In a sense, § 101 of the Patent Act can be thought of as the patent law analogy to the Bill of Rights of the Constitution. The latter sets in the broadest terms (“due process,” “equal protection”) the fundamental parameters of the citizenry’s legal right. In the context of patent law, § 101 similarly describes in the broadest terms the legally-protected subject matter an inventor can seek to patent: a “process, machine, manufacture, or composition of matter....” The Supreme Court has wisely adopted a policy of not deciding cases on broad constitutional grounds when they can be decided on narrower, typically statutorily limited, grounds.17 [1261]*1261Following the Supreme Court’s lead, courts should avoid reaching for interpretations of broad provisions, such as § 101, when more specific statutes, such as §§ 102, 103, and 112, can decide the case.
It is interesting to note that the United States in its amicus curiae brief to the Supreme Court in the Prometheus litigation — a long-running § 101 dispute that has had two trips to the Supreme Court from this court — noted to the Court, and indeed devoted part of its brief to, the likelihood that the disputed claims were invalid under §§ 102 or 103.18 The point being that, in complex cases such as that one, it is better to leave the question of validity to those specific provisions of the Patent Act which, as the Government states, “permit more nuanced factual distinctions [and] are the principal tools that Congress has provided for ‘drawing a line between the things which are worth to the public the embarrassment of an exclusive patent, and those which are not.’ ” Id. at 32, 111 S.Ct. 2123 (citing Graham v. John Deere Co. of Kansas City, 383 U.S. 1, 9, 86 S.Ct. 684, 15 L.Ed.2d 545 (1966) quoting Thomas Jefferson). What a waste of time and resources it would prove to be if the dispute between the Prometheus parties eventually gets resolved on the grounds the Government predicts.
Adopting this practice would also preclude § 101 claims from becoming the next toss-in for every defendant’s response to a patent infringement suit, particularly in business method litigation. We wrestled for years with the toss-in problem when defendants claimed “inequitable conduct” in just about every infringement case. Only recently did we finally fashion the stopper, which we hope will work. Therasense, Inc. v. Becton, Dickinson & Co., 649 F.3d 1276 (Fed.Cir.2011).19 We need not go through a similar exercise with § 101.
Does this mean that § 101 can never be raised initially in a patent infringement suit? No. For one, in certain technology fields, and particularly when laws of nature or physical phenomena are the issue, efficiency may dictate applying the coarse filter of § 101 first to address legitimate questions of patent eligibility. See, e.g., Ass’n for Molecular Pathology, 653 F.3d 1329 (patentability of isolated DNA). Even when the patent invokes the abstractness issue, such as in a business method patent, if it is clear and convincing beyond peradventure — that is, under virtually any meaning of “abstract” — that the claim at issue is well over the line, then a case could be made for initially addressing the § 101 issue in the infringement context.
But that latter patent would be a rather unusual and infrequent circumstance. More often, when the question of abstractness is presented in its usual abstract [1262]*1262terms, the trial court could as a matter of case management summarily put aside the § 101 defense on whatever grounds seem applicable in the case. The litigants will then be left to address the invalidity defenses of §§ 102, 103, and 112, as the statute provides, and the litigants, the trial court, and this court on review would have some semblance of a chance at arriving at a predictable and understandable result.20
In the case before us, for all these reasons the proper course of action is the one that the trial court and the panel majority has followed: decide the case on the question of compliance with §§ 102 and 103 as Congress has instructed, and decline the dissent’s invitation to put the parties and this court in the swamp that is § 101 jurisprudence.
4. Other Issues
GraphOn raises a number of other issues regarding which it also finds fault with the trial court’s determinations. We find none of them persuasive, nor, in the face of the invalidity determination set forth above, in any way determinative.
GraphOn first asserts that the district court improperly concluded that the MBB stored images. According to GraphOn, the MBB did not actually store images, but instead it stored hyperlinks to places where the images could be retrieved. Consequently, because the image itself was not stored in the MBB database GraphOn argues that it cannot invalidate the claims.
We are not persuaded by this argument. It is undisputed that the MBB had the ability to include a user-supplied image. MySpace, Inc., 756 F.Supp.2d at 1238. Based on the trial court’s construction of the term “image,” which has not been appealed, whether an image is displayed by physically storing the image in the database or storing a hyperlink in the database is irrelevant. We also agree with the trial court that even if the MBB somehow did not describe the image limitation due to its use of hyperlinks, it would have been obvious to one of ordinary skill in the art to have modified the database to allow for the uploading of actual images.
GraphOn also takes issue with the trial court’s analysis of whether “transaction ID,” a claim limitation found in the claims of the '538 Patent, was anticipated or rendered obvious by the MBB. The court adopted the parties’ proposed definition that “transaction ID” means “a unique identifier for a particular database entry.” Id. at 1239. GraphOn argues that because the transaction IDs of the MBB would sometimes be reused, they were not unique. GraphOn also alleges that in order to make changes to an entry in the MBB, the entire entry had to be deleted and recreated. Because the newly created entry did not necessarily have the same transaction ID as the original entry, GraphOn argues that the transaction ID did not continue throughout the life of the MBB entry.
Again, we are not persuaded by either of these positions. The trial court concluded, and we agree, that MBB entries maintained the same transaction ID number for the life of the entry and there is no evidence indicating that the same transaction ID would appear more than once in the MBB at a given time. Id. at 1240. Thus, [1263]*1263there is no error in the court’s conclusion that no triable issue of fact exists regarding the “transaction ID” limitation.
GraphOn further argues that the district court erred in its determination “that at least one user of the MBB used a password to restrict access to an entry.” Id. at 1241. GraphOn’s position appears to be that because the password protection feature in the MBB did not prevent the administrator from deleting entries, there is an issue of material fact as to whether the MBB’s password feature constituted password protection as used in the claims. Again, we disagree with GraphOn. The court adopted the parties’ agreed upon construction that “password protecting” means “restricting access to the data by means of a password.” Id. at 1240. We agree with the trial court that this construction “does not require that the system require passwords in all instances, or that the system restrict access by all other users.” Id.
Lastly, GraphOn asserts that the district court erred in its determination that the MBB describes the “update” and “modify” limitations contained within the '940 and '034 patents. Specifically, GraphOn asserts that MBB entries were not actually “updated” when users made changes to existing entries, but instead they were replaced. The entry was dropped from the file system and replaced with a new entry. We agree with the trial court that the specification does not require the updating to be carried out in any particular manner. Id. at 1242. Consequently, the fact that an MBB entry was replaced in the file system as opposed to being edited makes no difference in the validity analysis.
For the aforementioned reasons, we find no error in the trial court’s determinations regarding these issues.
Finally, GraphOn asserts broadly that the district court erred in its application of the Graham factors used for determining whether a patent can be invalidated for obviousness, arid in particular with regard to evidence of secondary considerations of nonobviousness. In Graham the Supreme Court held that four factual findings should be made before invalidating a patent for obviousness: (1) the scope and content of the prior art; (2) the level of ordinary skill in the art; (3) the differences between the claimed invention and the prior art; and (4) secondary considerations of nonobviousness. Graham v. John Deere Co. of Kansas City, 383 U.S. 1, 17-18, 86 S.Ct. 684, 15 L.Ed.2d 545 (1966). GraphOn asserts that the district court failed to make specific findings on each of these Graham factors in its summary judgment opinion and that this lack of specific findings implies that the court erred.
We do not require that district courts enumerate each of the Graham factors when making an obviousness determination. “Where the record adequately supports the judgment, the district court does not have an obligation to recite every detail of its reasoning.” Lexion Med., LLC v. Northgate Techs., Inc., 641 F.3d 1352, 1359 (Fed.Cir.2011). While it would certainly assist the parties and the appeals court if the district court more clearly recited its reasoning regarding each of the Graham factors, we do not wish to overburden our trial courts when the record establishes that the evidence was properly before and considered by the court. See Specialty Composites v. Cabot Corp., 845 F.2d 981, 990 (Fed.Cir.1988) (“It would have been preferable if the court had enumerated the Graham factors and systematically presented its analysis in terms of these factors. However, there is no reversible error if the required factual deter[1264]*1264minations were actually made and it is clear that they were considered while applying the proper legal standard of obviousness.”); see also Apple Computer, Inc. v. Articulate Systems, Inc., 234 F.3d 14, 26 (Fed.Cir.2000) (“A failure to enumerate and analyze the Graham factors explicitly is not necessarily reversible error, provided the proper factual determinations were made and the court considered them in rendering its conclusion of obviousness.”). Here, the parties presented extensive arguments both through their briefs and during the hearing regarding the Graham factors and, in particular, GraphOn’s assertions of secondary considerations of nonobviousness. Seeing no error in the trial court’s handling of this evidence, we affirm.
Conclusion
For the foregoing reasons, we affirm the district court’s order granting summary judgment of invalidity of the patents-in-suit.
AFFIRMED.