Access Official Technical PDF

Share Summary:LinkedInEmail

Patent infringement disputes over software can turn on detailed questions about how a feature behaves—not simply what a product is called or what it is designed to do. A post-trial ruling in the long-running VirnetX–Apple case illustrates how courts assess technical evidence about network services, software configurations and device capability. Although the case concerned Apple’s FaceTime and VPN On Demand features, its treatment of software behavior offers useful context for industrial automation teams developing connected products and systems.

Patent infringement claims focused on software behavior

VirnetX accused Apple of infringing patents covering secure communications. The dispute involved multiple versions of FaceTime and VPN On Demand, a feature that could establish a virtual private network (VPN) under specified conditions. After an April 2018 jury trial, jurors found that the accused versions of both features infringed the asserted patents and awarded approximately $502.6 million in damages. The jury also found willful infringement.

Apple asked the court to overturn the verdict or order a new trial. The court’s review was not a fresh determination of which technical account it found more persuasive. Under the legal standard described in the opinion, it had to consider whether substantial evidence supported the jury’s findings, draw reasonable inferences in favor of the verdict and avoid reweighing evidence or making credibility decisions reserved for jurors.

FaceTime: an “indication” need not be an IP address

One dispute concerned whether FaceTime’s server system provided an indication that it supported establishing a secure communication link. The court had construed “indication” to mean something beyond merely returning requested DNS records, such as an IP address or certificate. Apple argued that a callee’s IP address was necessary to establish a direct call and that the relevant message did not provide the required indication.

VirnetX’s expert described an “accept push” message as the culmination of a provisioning process. According to the testimony cited by the court, that process involved authenticating participants and devices, and the message included items such as certificates, tokens and other information. The expert characterized the message as indicating that the servers had completed provisioning and supported a direct, secure call. The court found this testimony, along with other trial evidence, sufficient to support the jury’s conclusion.

The court also rejected the premise that the indication had to include an IP address. Its claim construction required more than the mere return of an address; it did not require an address to be returned. The parties’ experts disagreed about whether the message indicated support for direct communication, but the court would not replace the jury’s assessment of that conflicting technical testimony with its own.

For engineers, the distinction is a reminder that a system’s compliance with a technical requirement may depend on the full behavior and context of a message or process—not just the presence or absence of one data field. In a dispute, documentation that explains how components interact can become important evidence.

VPN On Demand: configurations and conditional behavior mattered

The VPN On Demand claims concerned a process involving a DNS request, a determination about whether the requested site was secure, and—under specified conditions—the automatic creation of a VPN. Apple argued that the redesigned feature did not meet those requirements. It challenged, among other things, how the feature used an HTTPS probe, whether its behavior depended on network location, and whether it resembled an earlier noninfringing “If Needed” mode.

The court found that the trial record contained evidence supporting VirnetX’s account. Its expert testified that the system compared a requested domain name with a configured list and considered the result of the HTTPS probe. The court also cited testimony that a failed probe could indicate that a target server behind a firewall required authorization for access. The fact that the probe was location-based did not, on its own, defeat the infringement theory under the court’s construction of “secure server.”

Nor did the court accept Apple’s proposed requirement that the patents called for DNS requests to be intercepted before transmission to a DNS server. Because that temporal limitation had not been adopted as part of the claim construction, the court declined to introduce it for the first time after trial. This underscores the importance of clearly identifying disputed technical terms and limitations before a case reaches a jury.

Capability, actual operation and test records

The opinion distinguishes method claims from an apparatus claim. For the method claims, the court considered evidence that Apple tested VPN On Demand, including an internal email describing a test plan involving the HTTPS probe. The jury could reasonably infer that the planned testing took place. The court also noted that a method claim may be infringed by even one instance in which all required steps are performed.

For the apparatus claim, the court concluded that the relevant question included whether the device was capable of operating in the claimed mode. It also pointed to the test-plan evidence as circumstantial evidence of actual use. These findings do not mean that every optional feature or theoretical operating mode establishes infringement. The opinion discusses the claims and evidence in this particular case; it emphasizes that the claim language and the nature of the accused product guide the analysis.

Practical implications for automation teams

Industrial automation products increasingly combine software, network services and configurable operating modes. This case does not establish that any particular automation function infringes a patent. It does, however, provide a focused example of the kinds of technical questions that can arise when software behavior is disputed:

  • Describe system behavior precisely. Record how messages, servers, clients and network conditions interact, rather than relying only on feature names or high-level descriptions.
  • Track configuration and operating modes. Distinctions between versions or modes may be relevant, but comparisons do not replace analysis of the patent claims themselves.
  • Preserve test documentation. Test plans, implementation records and internal technical communications may help explain how a feature was designed or used.
  • Separate capability from execution. Whether a claim addresses a device capable of a function or a method that must be performed depends on its wording.

Conclusion

The VirnetX–Apple ruling shows how granular technical evidence can shape a patent infringement dispute: the meaning of a message, the effect of network location, the operation of a probe and the evidence of testing all mattered to the court’s review of the verdict. For industrial automation decision-makers, the practical lesson is to maintain clear records of software functions, configurations and tests, and to evaluate patent questions against the specific claim language and system behavior at issue.

Access Official Technical PDF

About The Author