throbber
Trials@uspto.gov
`571-272-7822
`
`
`
`
`Paper 9
`Date: December 27, 2019
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`_______________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`_______________
`
`GUEST TEK INTERACTIVE ENTERTAINMENT LTD.,
`Petitioner,
`
`v.
`
`NOMADIX, INC.,
`Patent Owner.
`_______________
`
`IPR2019-01191
`Patent 8,606,917 B2
`_______________
`
`
`
`
`
`Before SALLY C. MEDLEY, AMBER L. HAGY, and
`MATTHEW J. McNEILL, Administrative Patent Judges.
`
`
`
`
`
`HAGY, Administrative Patent Judge.
`
`
`
`DECISION
`Denying Institution of Inter Partes Review
`35 U.S.C. § 314, 37 C.F.R. § 42.4
`
`
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`I.
`
`INTRODUCTION
`
`Guest Tek Interactive Entertainment Ltd. (“Petitioner”) filed a
`
`Petition under 35 U.S.C. § 311 requesting inter partes review of claims 1
`
`and 11 (“the challenged claims”) of U.S. Patent No. 8,606,917 B2 (“the ’917
`
`patent”). Paper 1 (“Pet.”). Nomadix, Inc. (“Patent Owner”) filed a
`
`Preliminary Response. Paper 5 (“Prelim. Resp.”). With the Board’s
`
`authorization (Paper 6), Petitioner filed a Reply (Paper 7 (“Reply”)) and
`
`Patent Owner filed a Sur-Reply (Paper 8 (“Sur-Reply”)), both limited to
`
`addressing the priority date of the ’917 patent and whether the Board should
`
`exercise its discretion under 35 U.S.C. § 314(a) to deny institution in light of
`
`pending district court litigation. See Paper 6, 4 (authorizing limited
`
`briefing).
`
`Section 314(a) does not authorize institution of review unless
`
`Petitioner demonstrates a reasonable likelihood that it will prevail with
`
`respect to at least one challenged claim. 35 U.S.C. § 314(a). Applying that
`
`standard on behalf of the Director (37 C.F.R. § 42.4(a)), we do not institute
`
`the petitioned review.
`
`Petitioner presents three grounds of unpatentability, two of which rely
`
`on the Trudeau reference (Ex. 1004, U.S. Patent No. 8,046,578 B1, issued
`
`October 25, 2011 (“Trudeau ’578”)), as prior art. Pet. 5. Petitioner
`
`acknowledges the ’917 patent asserts priority to the October 20, 2000, filing
`
`date of U.S. Patent Application No. 09/693,060 (Ex. 1003, “the ’060
`
`application”) via a series of continuation applications. Id. at 12. Petitioner
`
`asserts Trudeau ’578 is nonetheless prior art to the ’917 patent because the
`
`’060 application lacks written description support for at least two limitations
`
`of the challenged claims of the ’917 patent. Id. at 12–18.
`
`2
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`Having reviewed all of the submissions by the parties, we determine
`
`Petitioner fails to demonstrate that the challenged claims of the ’917 patent
`
`lack written description support in the cited priority documents. Therefore,
`
`the Petition fails to establish Trudeau ’578 is prior art to the ’917 patent and,
`
`consequently, fails to demonstrate a reasonable likelihood of success as to
`
`Grounds 1 and 2. We do not reach the other issues raised in the Petition and
`
`the Preliminary Response as to Grounds 1 and 2. We also determine
`
`Petitioner has not demonstrated a reasonable likelihood of success as to
`
`Ground 3, for the reasons stated herein.
`
`II. BACKGROUND
`
`A. Real Parties in Interest and Related Proceedings
`
`Petitioner identifies itself as the real party-in-interest. Pet. 2.
`
`Nomadix identifies itself as the real party-in-interest. Paper 3, 1.
`
`Pursuant to 37 C.F.R. § 42,8(b)(2), both parties identify as a “related
`
`matter” the following co-pending litigation in the United States District
`
`Court for the Central District of California: Nomadix, Inc. v. Guest Tek
`
`Interactive Entertainment Ltd., Case 2:16-CV-08033-AB-FFM (“the
`
`Litigation”). Pet. 3; Paper 3, 1. Patent Owner additionally identifies several
`
`other litigations filed between 2004–2014, but does not indicate what patents
`
`are or were at issue or whether any of those proceedings remain pending.
`
`Paper 3, 2.
`
`Both parties also identify several petitions filed by Petitioner for
`
`review of patents that both parties indicate are “related” to the ’917 patent.
`
`Pet. 3; Paper 3, 1. Of such petitions, IPR2018-00376, IPR2018-00392,
`
`IPR2018-01660, and IPR2018-01668 have been denied, and IPR2019-00211
`
`and IPR2019-00253 have been instituted and are pending.
`
`3
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`B.
`
`’917 Patent
`
`The ’917 patent is entitled “Systems and Methods for Providing
`
`Content and Services on a Network System,” and issued on December 10,
`
`2013. Ex. 1001, codes (54), (45). The ’917 patent issued from U.S. Patent
`
`Application No. 13/659,851 (“the ’851 application”), filed on October 24,
`
`2012. Id. at codes (21), (22). The ’917 patent claims priority to and
`
`incorporates by reference the following U.S. patent applications:
`
`13/566,904, 12/685,585, 11/427,143, 09/693,060, 09/458,602, 09/458,569,
`
`60/161,189, 60/161,182, 60/161,181, 60/161,139, 60/161,093, 60/160,973,
`
`60/160,890, and 60/111,497. Id. at 1:8–51. As noted above, of particular
`
`relevance to our determination here is the ’060 application, which was filed
`
`on October 20, 2000, and claims priority to and incorporates by reference
`
`several applications, including U.S. Provisional Application No. 60/160,890
`
`(“the ’890 provisional”), filed October 22, 1999. Ex. 1003, 2, 9.1
`
`The ’917 patent describes “a method and system for selectively
`
`implementing and enforcing Authentication, Authorization and Accounting
`
`(AAA) of users accessing a network via a gateway device.” Ex. 1001, 8:8–
`
`11. Users may be, for example, guests of a hotel attempting to access an
`
`Internet site from their laptop in their hotel room. Id. at 3:15–18, 4:56–57.
`
`The system includes a network access controller that receives a request in
`
`TCP format from a source computer, such as a user laptop, for access to the
`
`Internet or other network. Id. at 3:57–61. Figure 1 of the ’917 patent
`
`illustrates the computer system, and is reproduced below.
`
`
`1 References herein to the page numbers of Exhibit 1003 are to the numbers
`added by Petitioner to the document in the lower left hand corner of each
`page, not to the original page numbers.
`
`4
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`
`
`
`
`Figure 1 of the ’917 patent “is a block diagram of a computer system
`
`that includes [an] AAA server for authenticating, authorizing and accounting
`
`sources accessing networks and/or online services . . . .” Id. at 5:24–26. As
`
`illustrated in Figure 1, the computer system includes “a plurality of
`
`computers 14 that can communicate with one or more online services 22 or
`
`networks via a gateway device 12 . . . .” Id. at 18:15–19. Gateway device
`
`12 “includes the ability to recognize computers attempting to access a
`
`network 12, the location of computers attempting to access a network, the
`
`identity of users attempting to gain network access, and additional attributes
`
`. . . .” Id. at 18:29–33.
`
`According to the ’917 patent, gateway device 12 may identify the
`
`source computer by “one or more attributes” contained within data packets
`
`transmitted to the gateway device by the source computer. Id. at 19:5–14.
`
`The attributes contained in such data packets “can include network
`
`information, source IP address, source port, link layer information, source
`
`5
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`MAC address, VLAN tag, circuit ID, destination IP address, destination
`
`port, protocol type, packet type, and the like.” Id. at 23:41–45.
`
`The operation of the AAA server is illustrated in Figure 2 of the ’917
`
`patent, which is reproduced below.
`
`
`Figure 2 of the ’917 patent is a “flow chart of a method in which [an]
`
`AAA server performs authentication, authorization, and accounting,
`
`according to one aspect of the invention.” Id. at 5:28–30. The ’917 patent
`
`states that “as used herein authentication refers to the identification of the
`
`source, authorization refers to the determination of permittable source
`
`access, and accounting refers to the tracking of a source’s access to a
`
`network.” Id. at 19:17–21 (emphasis added).
`
`6
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`As illustrated in Figure 2, a source attempting to access a network is
`
`authenticated based on an “attribute” sent by the source in a packet. Id. at
`
`Fig. 2 (block 200), 19:5–8, 23:33–35. In identifying a source based on an
`
`attribute sent in a packet, the AAA server is able to automatically identify
`
`the source device “in a manner that is transparent to computer users” (that is,
`
`without requiring a user to enter an ID). Id. at 21:27–31, 21:42–44. This
`
`process is described as follows, with reference to Figure 2:
`
`In operation, a source computer requests (block 200) access to a
`network, destination, service, or the like. Upon receiving a
`packet transmitted to the AAA server 30, the AAA server 30
`examines the packet to determine the identity of the source
`(block 210). The attributes transmitted via the packet are
`temporarily stored in the source profile database so that the data
`can be examined for use in determining authorization rights of
`the source.
`
`Id. at 23:33–45. The attributes “include network information, source IP
`
`address, source port, link layer information, source MAC address, VLAN
`
`tag, circuit ID, destination IP address, destination port, protocol type, packet
`
`type, and the like.” Id. at 23:41–45.
`
`After source information is identified and stored, access requested
`
`from a source is matched against the authorization of that source. Id. at
`
`23:45–47. As indicated in Figure 2, authorization of a source may be based
`
`on an attribute associated with any one of source, destination, or content. Id.
`
`at Fig. 2 (block 220), 22:61–65. According to one aspect of the invention,
`
`the authorization capability of the AAA server 30 can be based
`upon the type of services the source is attempting to access,
`such as a destination address, identified by the gateway device
`12 based upon data received from the source computer. The
`destination can be a destination port, Internet address, TCP
`port, network, or the like. Moreover, the authorization
`
`7
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`capability of the AAA server 30 can be based upon the content
`type or protocol being transmitted. According to the system
`and method of the present invention, each packet can be filtered
`through the selective AAA process, so that any or all sources
`can be authorized access to a particular destination based on the
`access rights associated with the respective sources.
`
`Id. at 22:61–23:6.
`
`C. Challenged Claims
`
`Claims 1 and 11 are challenged. Claim 1 is reproduced below,
`
`adopting the lettering and formatting as added by Petitioner (Pet. 7–8):
`
`A method for granting access to a computer network,
`comprising:
`
`[1.A] receiving at an access controller a request to access the
`network from a source computer, the request including a
`transmission control protocol (TCP) connection request having
`a source IP address and a destination IP address;
`
`[1.B] determining by the access controller whether the source
`computer must login to access the network, including:
`
`[1.C] comparing the source IP address with profiles of
`authorized source devices, each profile including an IP address,
`wherein if the source IP address is included in a profile of an
`authorized source device, the source device is granted access
`without further authorization, and
`
`[1.D] if the source IP address is not included in a profile
`associated with an authorized source device, then determining
`whether the destination IP address is included in a plurality of
`destination IP addresses associated with the access controller,
`wherein if the destination IP address is included in the plurality
`of destination IP addresses, the source device is granted access
`without further authorization, and
`
`[1.E] if the destination IP address is not included in the plurality
`of destination IP addresses, then the access controller
`
`8
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`determines the source device must be authorized to access the
`network and provides the source device with a login page;
`
`[1.F] using the access controller to authenticate credentials
`provided from the source device via the login page; and
`
`[1.G] authorizing the source device access to the network if the
`provided credentials are authenticated.
`
`As noted by Petitioner, claim 11 recites mostly the same claim
`
`limitations in system form. Pet. 8. The parties argue claims 1 and 11
`
`collectively.
`
`D. Asserted Grounds of Unpatentability
`
`Petitioner asserts that the challenged claims are unpatentable based on
`
`the following grounds (Pet. 5):
`
`Claims Challenged
`1, 11
`1, 11
`1, 11
`
`35 U.S.C. §
`103(a)
`103(a)
`103(a)
`
`References
`Trudeau ’578, Whyte2
`Trudeau ’578, Whyte, Fuh ’4743
`Fuh ’474, NIST4
`
`
`As further support, Petitioner relies on the Declaration of Dr. Peter
`
`Dordal. Ex. 1002. Patent Owner relies on the Declaration of Stuart G.
`
`Stubblebine, Ph.D. Ex. 2006.
`
`
`2 Whyte, D., Kranakis, E., and van Oorschot, P.C., “DNS-based Detection of
`Scanning Worms in an Enterprise Network, Proceedings of the 12th Annual
`Network and Distributed System Security Symposium,” San Diego, CA
`(Feb. 3–4, 2005) (Ex. 1005, “Whyte”).
`
`3 Fuh et al., U.S. Patent No. 6,463,474 B1, filed July 2, 1999, issued Oct. 8,
`2002 (Ex. 1006, “Fuh ’474”).
`
`4 Wack, J. and Carnahan, L., “Keeping Your Site Comfortably Secure: An
`Introduction to Internet Firewalls,” NIST Special Pub. 800-10 (Dec. 1994)
`(Ex. 1007, “NIST”).
`
`9
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`III. ANALYSIS
`
`A. Principles of Law
`
`A patent claim is unpatentable under 35 U.S.C. § 103(a) if the
`
`differences between the claimed subject matter and the prior art are such that
`
`the subject matter, as a whole, would have been obvious at the time the
`
`invention was made to a person having ordinary skill in the art to which said
`
`subject matter pertains. KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406
`
`(2007). The question of obviousness is resolved on the basis of underlying
`
`factual determinations including: (1) the scope and content of the prior art;
`
`(2) any differences between the claimed subject matter and the prior art;
`
`(3) the level of ordinary skill in the art; and (4) when in evidence, objective
`
`evidence of nonobviousness.5 Graham v. John Deere Co., 383 U.S. 1,
`
`17–18 (1966).
`
`“In an [inter partes review], the petitioner has the burden from the
`
`onset to show with particularity why the patent it challenges is
`
`unpatentable.” Harmonic Inc. v. Avid Tech., Inc., 815 F.3d 1356, 1363 (Fed.
`
`Cir. 2016) (citing 35 U.S.C. § 312(a)(3) (requiring inter partes review
`
`petitions to identify “with particularity . . . the evidence that supports the
`
`grounds for the challenge to each claim”)). This burden of persuasion never
`
`shifts to Patent Owner. See Dynamic Drinkware, LLC v. Nat’l Graphics,
`
`Inc., 800 F.3d 1375, 1378 (Fed. Cir. 2015) (discussing the burden of proof in
`
`inter partes review).
`
`
`5 Patent Owner does not present arguments or evidence of such secondary
`considerations in its Preliminary Response. Therefore, secondary
`considerations do not constitute part of our analysis herein.
`
`10
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`B. Level of Ordinary Skill in the Art
`
`Relying on the testimony of Dr. Dordal, Petitioner describes the level
`
`of ordinary skill as follows:
`
`A person of ordinary skill in the art at the time of the alleged
`inventions of claims 1 and 11 (“POSITA”) would have had
`(1) either a formal degree in computer science or a related
`subject, or commensurate informal education in computer
`programming and designing computer networks, and (2) at least
`2 years of experience in designing or programming computer
`networks.
`
`Pet. 19 (citing Ex. 1002 ¶ 57). Petitioner further asserts “[a]ccording to Dr.
`
`Dordal, this definition would have been the same regardless of the priority
`
`date of the ’917 patent (e.g., whether the ’917 patent’s 2012 filing date, or
`
`October 1999, the date of the ’890 provisional).” Id.
`
`Patent Owner does not propose an alternative assessment. To the
`
`extent necessary, and for purposes of this Decision, we accept the
`
`assessment offered by Petitioner as it is consistent with the ’917 patent and
`
`the asserted prior art.
`
`C. Claim Construction
`
`Because this Petition was filed after November 13, 2018, the effective
`
`date of a change to our rules, we interpret the claims of the ’917 patent
`
`according to that new rule, wherein we “us[e] the same claim construction
`
`standard that would be used to construe the claim in a civil action under
`
`35 U.S.C. [§] 282(b), including construing the claim in accordance with the
`
`ordinary and customary meaning of such claim as understood by one of
`
`ordinary skill in the art and the prosecution history pertaining to the patent.”
`
`See Changes to the Claim Construction Standard for Interpreting Claims in
`
`Trial Proceedings Before the Patent Trial and Appeal Board, 83 Fed. Reg.
`
`11
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`51,340, 51,358 (Oct. 11, 2018) (codified at 37 C.F.R. § 42.100(b) (2019)).
`
`Petitioner offers a construction of the term “profile,” which appears in
`
`both challenged claims, as meaning “a collection of attributes associated
`
`with a specific device.” Pet. 18. Patent Owner does not offer a different
`
`construction, but notes that the district court in the Litigation construed
`
`“profiles” to mean “a collection of attributes associated with [a] source
`
`device[s].”6 Prelim. Resp. 9 (citing Ex. 2004, 23). Patent Owner further
`
`notes that its arguments do not depend on construction of the term “profile.”
`
`Id.
`
`We determine that no explicit construction of “profile,” or any other
`
`claim term, is needed to resolve the issues presented by the arguments and
`
`evidence of record. See Nidec Motor Corp. v. Zhongshan Broad Ocean
`
`Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (per curiam) (claim terms
`
`need to be construed “only to the extent necessary to resolve the
`
`controversy” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d
`
`795, 803 (Fed. Cir. 1999))).
`
`D. Grounds Based on Obviousness over Trudeau ’578
`
`In Grounds 1 and 2, Petitioner asserts the challenged claims are
`
`unpatentable as obvious over Trudeau ’578 (1) in combination with Whyte
`
`(Ground 1), or (2) in combination with Whyte and Fuh ’474 (Ground 2).
`
`Pet. 5. Central to both grounds is whether Trudeau ’578 is prior art to the
`
`’917 patent, an issue that turns on whether the ’917 patent is entitled to
`
`priority to the filing date of the ’060 application via a chain of continuation
`
`
`6 Patent Owner’s quote of the district court’s construction omits the word
`“associated”; we view this omission as an inadvertent typographical error.
`
`12
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`applications. Pet. 11–18; Prelim. Resp. 11–28. As discussed below, this
`
`issue is dispositive of Grounds 1 and 2.
`
`1. Priority Date of the ’917 Patent
`
`a. Legal Standards for Establishing Priority
`
`As noted above, in an inter partes review, the burden of persuasion is
`
`on the petitioner to prove unpatentability by a preponderance of the
`
`evidence, and that burden never shifts to the patent owner. Dynamic
`
`Drinkware, 800 F.3d at 1378. The petitioner also has the initial burden of
`
`production to show that an asserted reference qualifies as prior art under
`
`35 U.S.C. § 102. Id. at 1378–79. Once the petitioner has met that initial
`
`burden, the burden of production shifts to the patent owner to argue or
`
`produce evidence that either the asserted reference does not render the
`
`challenged claims unpatentable, or the reference is not prior art. Id. at
`
`1379–80 (citing Tech. Licensing Corp. v. Videotek, Inc., 545 F.3d 1316,
`
`1327 (Fed. Cir. 2008)). Once the patent owner has met that burden of
`
`production in demonstrating, for example, entitlement of the challenged
`
`claims to a filing date that antedates the asserted reference, the burden of
`
`going forward again shifts to the petitioner to persuade the Board that the
`
`challenged claims are not entitled to the benefit of the earlier filing date. See
`
`id. at 1328 (describing burdens in the context of an invalidity challenge in
`
`district court).
`
`Pursuant to 35 U.S.C. § 120, the ’917 patent is entitled to assert
`
`priority to the filing date of the ’060 application only if the ’060 application
`
`discloses the invention claimed in the ’917 patent in the manner provided by
`
`13
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`35 U.S.C. § 112(a).7 Thus, to satisfy its burden of production here, Patent
`
`Owner must produce sufficient evidence and argument to show that the
`
`asserted priority application contains a written description that supports all
`
`limitations of the challenged claims. See Tech. Licensing Corp., 545 F.3d at
`
`1327. The test for sufficiency of a written description under 35 U.S.C.
`
`§ 112(a) is whether the earlier application’s disclosure “reasonably conveys
`
`to those skilled in the art that the inventor had possession of the claimed
`
`subject matter as of the filing date.” Ariad Pharms., Inc. v. Eli Lilly & Co.,
`
`598 F.3d 1336, 1351 (Fed. Cir. 2010) (en banc). The written description
`
`“test requires an objective inquiry into the four corners of the specification
`
`from the perspective of a person of ordinary skill in the art.” Id.
`
`b. Overview of the Priority Dispute
`
`Petitioner’s reliance on Trudeau ’578 as prior art to the ’917 patent is
`
`premised upon the assertion that the ’060 application (which antedates
`
`Trudeau ’578) fails to provide written description support for claims 1 and
`
`11 of the ’917 patent. See Pet. 12–13. The relationship between the
`
`application for the ’917 patent (the ’851 application) and the ’060
`
`
`7 We cite to the post-AIA version of § 112, because the application that
`issued as the ’917 patent was filed on February 28, 2013, after the AIA
`amendments to § 112 took effect on September 16, 2012. See Leahy-Smith
`America Invents Act (“the AIA”), Pub. L. No. 112-29, § 4(e), 125 Stat. 284,
`297 (2011) (amendments to § 112 “shall take effect upon the expiration of
`the 1-year period beginning on the date of the enactment of this Act and
`shall apply to any patent application that is filed on or after that effective
`date”) (emphasis added). However, our Decision is not affected by the
`changes to § 112 enacted via the AIA; we would reach the same result
`applying either the pre-AIA version or the post-AIA version.
`
`
`14
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`application is illustrated below:
`
`
`The above graphic, reproduced from the Preliminary Response, is a
`
`representation of the asserted priority chain between linking the ’060
`
`application to the ’851 application. See Prelim. Resp. 4.
`
`As illustrated above, the ’851 application asserts priority, through a
`
`chain of continuation applications, to the ’060 application filed on October
`
`20, 2000. If Petitioner is correct, however, in asserting that the ’060
`
`application lacks written description support for claims 1 and 11 of the ’917
`
`patent, then those claims would not be entitled to a filing date that antedates
`
`Trudeau ’578. Rather, the next earliest asserted priority date for the ’917
`
`patent is the June 28, 2006, filing date of application 11/427,143 (“the ’143
`
`application”) (see Ex. 1001, code (63)), which is after the latest filing date of
`
`the application for Trudeau ’578.8 In that event, Trudeau ’578 would be
`
`
`8 The application that issued as Trudeau ’578 was filed April 14, 2005, and
`claims priority to U.S. Provisional Application No. 60/562, 397, filed April
`14, 2004. Ex. 1004, codes (22), (60). In arguing the priority date of
`Trudeau, Petitioner references Trudeau’s 2005 filing date. Pet. 54. Neither
`
`15
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`prior art to the ’917 patent under 35 U.S.C. § 102(e). Patent Owner has not,
`
`on this record, come forward with any arguments or evidence to support
`
`antedating Trudeau ’578 on any basis other than asserting entitlement to the
`
`’060 application filing date. Because Patent Owner bears the burden of
`
`production on the priority issue (see Dynamic Drinkware, 800 F.3d at 1379–
`
`80), the only possible defect before us in Petitioner’s burden of showing that
`
`Trudeau ’578 is prior art is whether the ’917 patent claims are supported by
`
`written description in the ’060 application.
`
`Petitioner contends the ’060 application fails to provide written
`
`description support for the following limitations of claim 1 of the ’917
`
`patent, alone or in combination (using the reference numbers provided by
`
`Petitioner and also adopted by Patent Owner):
`
`[1.C] comparing the source IP address with profiles of
`authorized source devices, each profile including an IP address,
`wherein if the source IP address is included in a profile of an
`authorized source device, the source device is granted access
`without further authorization, and
`
`[1.D] if the source IP address is not included in a profile
`associated with an authorized source device, then determining
`whether the destination IP address is included in a plurality of
`destination IP addresses associated with the access controller,
`wherein if the destination IP address is included in the plurality
`of destination IP addresses, the source device is granted access
`without further authorization[.]
`
`Pet. 11–18. Petitioner raises the same contentions against similar limitations
`
`11[C] and 11[D]. See id. (arguing claims 1 and 11 collectively) Patent
`
`
`party addresses whether Trudeau would be entitled to the 2004 filing date of
`its provisional application, and we determine that point is not material to our
`analysis herein.
`
`16
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`Owner disputes these contentions. Prelim. Resp. 11–28 (also arguing claims
`
`1 and 11 collectively).
`
`
`
`In the Preliminary Response, Patent Owner provides a detailed
`
`mapping of the limitations of claims 1 and 11 to the ’060 application, which
`
`includes the ’890 provisional incorporated therein by reference. Prelim.
`
`Resp. 11–28. Petitioner addresses only limitations 1/11[C] and 1/11[D] in
`
`both the Petition and Reply.9 Pet. 11–18; Reply 6–10.
`
`
`
`We have reviewed the arguments and evidence submitted by both
`
`parties. We conclude Patent Owner has met its burden of production in
`
`demonstrating all limitations of the challenged claims of the ’917 patent are
`
`supported by written description in the ’060 application, and Petitioner has
`
`not rebutted that showing sufficiently to demonstrate a reasonable likelihood
`
`of prevailing on this issue. We address in detail below the parties’
`
`arguments and evidence as to the disputed limitations.
`
`c. The “Comparing the Source IP Address” Limitation (1/11[C])
`
`Petitioner argues the ’060 application fails to disclose this limitation
`
`because it does not disclose (1) comparing the source IP address of
`
`incoming packets with profiles of authorized source devices; (2) that each
`
`profile includes an IP address; or (3) that the source device is granted access
`
`without further authorization if its IP address is included in a profile.
`
`Pet. 13. Petitioner further argues (relying on the testimony of Dr. Dordal)
`
`that “the specific embodiments disclosed in the ’060 application involve
`
`accessing a source profile using a MAC address, User ID, or VLAN ID.
`
`
`9 Petitioner briefly states that “[m]any of the prior applications also fail to
`expressly disclose other limitations in claims 1 and 11,” but does not offer
`substantive analysis in the Petition or the Reply. See Pet. 17, n.3.
`
`17
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`They do not mention comparing source IP addresses against other IP
`
`addresses, let alone IP addresses in profiles.” Id. at 13–14 (emphasis added)
`
`(citing Ex. 1002 ¶¶ 27, 29–35).
`
`Patent Owner disputes each of Petitioner’s arguments, pointing to
`
`passages in the ’060 application that disclose storing “attributes” in a
`
`“source profile database,” wherein such attributes include a “source IP
`
`address,” and authenticating a source based on an attribute associated with
`
`the source. Prelim. Resp. 17–18. In particular, Patent Owner quotes the
`
`following passage:
`
`Upon receiving a packet transmitted to the AAA server 30, the
`AAA server 30 examines the packet to determine the identity of
`the source (block 210). The attributes transmitted via the
`packet are temporarily stored in the source profile database so
`that the data can be examined for use in determining
`authorization rights of the source. The attributes contained in
`the packet can include network information, source IP address,
`source port, link layer information, source MAC address,
`VLAN tag, circuit ID, destination IP address, destination port,
`protocol type, packet type, and the like. After this information
`is identified and stored, access requested from a source is
`matched against the authorization of that source (block 230).
`
`Id. (quoting Ex. 1003, 25:22–26:2). Patent Owner then contends “[t]his
`
`quoted disclosure makes clear that 1) attributes may be used to determine
`
`authorization rights of a source, and 2) a list of such attributes specifically
`
`includes the packet ‘source IP address.’” Id. at 18. Patent Owner
`
`additionally quotes several other passages describing attributes being stored
`
`in source profiles and authenticating a source by comparing stored source
`
`profiles with attributes received from a device to determine the device’s
`
`identity. Id. at 18–19 (quoting Ex. 1003, 13:5–13, 13:15–20, 14:5–11,
`
`18
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`21:3–6). Patent Owner also cites the ’890 provisional, incorporated by
`
`reference in the ’060 application,10 which describes entering “a subscriber
`
`profile into the database,” including entering an IP address. Id. at 19
`
`(quoting Ex. 1021, 10311).
`
`
`
`In its Reply, Petitioner concedes that the ’060 application discloses
`
`“the attributes transmitted via a packet may be stored in a source profile
`
`database for use in determining source authorization rights, and that the
`
`attributes contained in the packet can include network information, source IP
`
`address, MAC address, packet type, etc.” Reply 7. Petitioner argues,
`
`however, that this disclosure is inadequate to show possession of limitation
`
`1/11[C] because “[i]t does not suggest a comparison of the source IP
`
`address against multiple profiles of authorized source devices that each
`
`contain an IP address.” Id. (emphasis added). Petitioner further notes that
`
`the additional passages cited by Patent Owner do not contain this explicit
`
`disclosure (id. at 7–8), and contends “[a] ‘source IP address’ included in a
`
`profile, and comparing an ‘attribute’ against a source profile, do not amount
`
`to comparing a source IP address in a received packet against multiple
`
`profiles of authorized devices that each contain an IP address.” Id. at 8.
`
`
`
`Petitioner’s arguments appear to be premised on a lack of literal
`
`reproduction of the words of the disputed limitation in the ’060 application,
`
`which is not the proper legal standard. An ipsis verbis disclosure is not
`
`necessary to satisfy the written description requirement. Vas-Cath Inc. v.
`
`
`10 Petitioner does not dispute this point.
`
`11 References herein to the page numbers of Exhibit 1021 are to the numbers
`added by Petitioner to the document in the lower left hand corner of each
`page, not to original page numbers.
`
`19
`
`

`

`IPR2019-01191
`Patent 8,606,917 B2
`
`
`Mahurkar, 935 F.2d 1555, 1563 (Fed. Cir. 1991). The disclosure need only
`
`reasonably convey to persons skilled in the art that the inventor had
`
`possession of the subject matter in question, even if every nuance of the
`
`claims is not explicitly described in the specification. Id.; see also Ariad
`
`Pharm., 598 F.3d at 1351; Union Oil Co. v. Atlantic Richfield Co., 208 F.3d
`
`989, 1001 (Fed. Cir. 2000) (noting that the written

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket