Realvirt, LLC v. Lee

195 F. Supp. 3d 847, 2016 WL 3912855, 2016 U.S. Dist. LEXIS 94151
District Court, E.D. Virginia·Decided July 19, 2016·No. Case No. 1:15-cv-963·Published·Cited by 4 cases

Opinion

MEMORANDUM OPINION

T. S. Ellis, III, United States District Judge

In this 35 U.S.C. § 145 action, plaintiff challenges a United States Patent and Trademark Office (“PTO”) decision rejecting the patentability of the inventions claimed in U.S. Patent Application Serial No. 07/773, 161 (the “161 Application”). At issue on the parties’ cross-motions for summary judgment and the PTO’s motion to dismiss are (i) whether plaintiff has standing to bring a § 145 action, and (ii) if so, whether the inventions claimed in the 161 Application are patentable. As the matter has been fully briefed and argued orally, it is now ripe for disposition.

I.

The pertinent facts, derived from the parties’ statements of undisputed facts and the Administrative Record (“AR”), may be succinctly summarized.

Plaintiff Realvirt, LLC, a Delaware Corporation with its office in Massachusetts, is the purported assignee and owner of the 161 Application. Defendant Michelle K. Lee is the Under Secretary of Commerce for Intellectual Property and the Director of the PTO. Anthony Z. Bono (“Tony Bono”) and Joachim C.S. Martillo (“Joachim Martillo”) are two of the six declared inventors of the inventions claimed in the 161 Application. Tony Bono and Joachim Martillo purportedly assigned their rights to the 161 Application to plaintiff by virtue of a written document dated February 15, 2013.

A.

The 161 Application describes inventions related to a network switching device that connects computers through networks. As the 161 Application specification explains, bridges and routers are two types of network switching devices. A bridge is “a well known type of network switching device to which multiple branches of a network are connected”; a router, like a bridge, “switch[es data] packets between branches of a network,” but unlike a bridge, “operate[s] at the next higher level of network software, the so-called network layer, and ... provide[s] more flexibility and control of the actual route which the packet takes through the network.” AR at 5. The specification further explains that because bridges and routers have their own advantages and disadvantages, it is often desirable to configure a network by using a combination of bridges and routers.

The 161 Application claims a network switching device that is a “software configurable bridge/router.” AR at 8. This device provides a “software means” of enabling users to “group [] input/output devices [851] into one or more logical bridges” and to “connect the bridges with one or more logical routers.” AR at 7. The specification explains that a user may configure the bridge/router device through a “configuration routine,” as shown in Figure 8. See AR at 177. The configuration routine includes a number of menus that allow a user to select his desired configuration settings, and these settings can be stored in the data structures shown in Figures Sill. See AR at 173-76 (showing examples of various bridge/router configurations). Once a user enters his desired bridge/router configuration settings and once these settings are stored in data structures, the configuration settings may be implemented on the bridge/router device in one of two ways: (i) a “static” configuration, or (ii) a “dynamic” configuration.1 When the static configuration method is selected, the bridge/router device is reset, causing an initialization routine to run. The initialization routine “creates the data structures of FIGS. 9-11 in RAM, copies configuration data from NOVRAM into them,2 and then fills out or updatefe] the other fields of those data structures.” AR at 9-10. Then “the bridge/router ... prepare[s] to operate as configured by the user in the routine of FIG. 8.” Id. By contrast, when the dynamic configuration method is selected, the configuration settings for the bridge/router device are changed while the device is running—that is, without resetting the device.3

The ’161 Application includes numerous claims, and the parties agree that all claims in issue (1, 2, 5-16, and 18-39) rise or fall with representative claim 24, incorporating the features of claim 23 (“Claim 24”). Claim 24 describes “[a] network switching device comprising”:

(i) “a plurality of input/output devices • being configured to communicate packets”;
(ii) “a configuration routine that defines one or more logical bridges, wherein each of the one or more logical bridges includes one or more parts that provide one or more connections to a logical bridge, selectively associates each of said input/output devices with a selected one or more of said of [sie] logical bridges, and creates one or more data structures that represent which input/output devices have been associated with each logical bridge”;
(iii) “a bridging routine that responds to said one or more data structures by creating said one or more logical bridges with which one or more input/output devices have been associated to operate as one or more separate media access ■control level bridge including, and having a port for, each of the input/output devices represented as being associated with such logical bridge by said one or more data structures”; and
(iv) “at least one processing unit and associated memory to execute said configuration routine to create said one or [852] more data structures and said bridging routine to operate said one or more separate media access control level bridges”;4
(v) “at least one routing routine that responds to said one or more data structures representing which logical bridges have been associated with each logical router by causing one or more logical routers with which one or more logical bridges have been associated to operate as a separate network layer router having an interface to each of the logical bridges represented as being associated with such logical router by said one or more data structures.”

AR at 3005, Claims Appendix.

Although Claim 24 purports to recite a novel and non-obvious network switching device, the specification includes a minimal discussion of the hardware needed to build and operate the claimed invention. In this regard, the specification’s limited discussion of the hardware used for the network switching reflects the following:

Free access — add to your briefcase to read the full text and ask questions with AI

Realvirt, LLC v. Lee, 195 F. Supp. 3d 847, 2016 WL 3912855, 2016 U.S. Dist. LEXIS 94151 (E.D. Va. 2016).

195 F. Supp. 3d 847 (Realvirt, LLC v. Lee) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related