UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`VIPTELA, INC.
`Petitioner
`
`V.
`
`FATPIPE NETWORKS INDIA LIMITED,
`Patent Owner
`
`
`
`[filer Partes Review Case No. 2017-
`
`
`
`PETITION FOR INTER PARTES REVIEW OF US. PATENT NO. 6,775,235
`
`UNDER 35 U.S.C. §§ 311-319 AND 37 C.F.R. § 42.100
`
`
`
`8479466571
`
`FatPipe Exhibit 2001, pg. 1
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Paries Review
`
`US. Patent No. 6,775,235
`
`TABLE OF CONTENTS
`
`1.
`
`MANDATORY NOTICES .......................................................................... ..1
`
`A.
`B.
`C.
`
`D.
`E.
`F.
`
`Real Party-In-lnterest (37 C.F.R. § 42.8(b)(1)) ................................. ..1
`Related Matters (37 C.F.R. § 42.8(b)(2)) ........................................... ..1
`Lead and Backup Counsel (37 C.F.R. § 42.8(b)(3) and
`42.10(a)) ............................................................................................. ..2
`Service Information (37 C.F.R. § 42.8(b)(4)) .................................... ..3
`Payment of Fees (37 C.F.R. §§ 42.15(a) and 42.103(a)) ................... ..3
`Standing (37 C.F.R. § 42.104(a)) ....................................................... ..3
`
`II.
`
`OVERVIEW OF CHALLENGE AND RELIEF REQUESTED ................. ..3
`A.
`Publications Relied Upon ................................................................... ..3
`B.
`Grounds For Challenge ...................................................................... ..4
`
`III.
`
`RELEVANT INFORMATION CONCERNING THE CONTESTED
`
`PATENT ....................................................................................................... ..4
`
`A.
`B.
`
`C.
`
`Effective Filing Date of the ’235 Patent ............................................ ..4
`The ’235 Patent (Ex. 1001) ................................................................ ..5
`1.
`Overview of the ’235 Patent .................................................... ..5
`
`Prosecution History .................................................................. ..5
`2.
`Claim Construction ............................................................................ ..6
`
`1.
`2.
`
`Level of Ordinary Skill in the Art ............................................ ..6
`Patent Owner’s Proposed Constructions .................................. ..6
`
`IV.
`
`SUMMARY OF PRIOR ART AND REFERENCES RELIED ON ............ ..8
`
`A.
`B.
`
`Brief Summary of Karol (Ex. 1006) .................................................. ..8
`Brief Summary of Stallings (EX. 1011) .............................................. ..9
`
`V.
`
`A REASONABLE LlKELlHOOD EXISTS THAT THE
`
`CHALLENGED CLAIIVIS ARE UNPATENTABLE ................................. ..9
`
`A.
`
`Ground 1: Claims 4-1 1, l4, l9, and 22-24 of the ’235 Patent
`
`B.
`
`C.
`
`(Ex. 1001) are anticipated by Karol (Ex. 1006) ................................. ..9
`Ground 2: Claims 5, 6, 11-15, 19, 22, and 23 ofthe ’235 Patent
`
`are obvious over Karol (Ex. 1006) in view of Stallings (Ex.
`10] l) ................................................................................................. ..31
`Ground 3: Claims 4-15, 19, and 22-24 of the ’235 Patent (Ex.
`
`1001) are obvious over Karol (EX. 1006) ......................................... ..45
`
`VI.
`
`CONCLUSION ........................................................................................... ..60
`
`8479466571
`
`_ii_
`
`FatPipe Exhibit 2001, pg. 2
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Paries Review
`
`US. Patent No. 6,775,235
`
`TABLE OF AUTHORITIES
`
`Cases
`
`Amazoncom, Inc. v. Barnesandnoble.com, Inc, 239 F.3d 1343 (Fed. Cir. 2001)....7
`In re 'I‘ram'logic Tech, Inc, 504 F.3d 1249 (Fed. Cir. 2007) ................................. ..6
`In re ZIetz, 13 USPQ2d 1320 (Fed. Cir. 1989) ........................................................ ..7
`KSR v. Tefeflex, 550 US. 398 (2007) ............................................................ .. passim
`
`Statutes
`
`35 U.S.C. § 103 ........................................................................................................ ..4
`35 U.S.C. § 318(b) ................................................................................................. ..60
`35 U.S.C. §§ 311-319 .............................................................................................. ..1
`
`Other Authorities
`
`MPEP § 2143 ................................................................................................. .. passim
`
`Regulations
`37 C.F.R. § 42.8 ....................................................................................................... ..1
`37 C.F.R. §§ 42.100 ................................................................................................. ..1
`37 C.F.R. §§ 42.]03(a) ............................................................................................. ..3
`
`8479466571
`
`-iii-
`
`FatPipe Exhibit 2001, pg. 3
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`U.S. Patent No. 6,775,235
`
`PETITIONER’S EXHIBITS
`
`Exhibit No. Descri tion
`
`U.S. Patent No. 6,775,235 by Sanchaita Datta and Ragula Bhaskar
`entitled “Tools and Techniques for Directing Packets Over
`1001
`
`Disparate Networks” (“the 2315 Patent”)
`File Histor
`for U.S. Patent No. 6,775,235
`
`1002
`
`U.S. Patent No. 7,406,048 by Sanchaita Datta and Ragula Bhaskar
`entitled “Tools and Techniques for Directing Packets Over
`1003
`
`Disparate Networks” (“the ’048 Patent”)
`File Histo
`for U.S. Patent No. 7,406,048
`1004
`
`Declaration of Dr. Leonard J. mes
`U.S. Patent No. 6,628,617 by Mark John Karol and Malathi
`Veeraraghavan entitled “Technique for Intemetworking Traffic on
`
`Connectionless and Connection-Oriented Networks” (“Karol”)
`W.R. Stevens, “TCP/IP Illustrated Volume 1, the Protocols,”
`
`Addison-Wesley Professional Computing Series, 1994, ISBN—0-
`
`201 -63346—9 (“Stevens”).
`Complaint, D.I. 1 in 1:16- cv-00182-LPS in the District of Delaware
`U.S. Patent No. 6,748,439 by David R. Monachello et al. entitled
`“System and Method for Selecting Internet Service Providers from a
`Workstation that is Connected to a Local Area Network”
`
`
`
`“Monachello”)
`
`
`
`An] 29, 2016)
`
`1
`Petition for Inter Fortes Review, IPR2016-00976, Paper No.
`William Stallings, “Data and Computer Communications,” Prentice-
`Hall, 5th Edl’tlon, 1997, ISBN-81-203-1240-6, “Stallms”
`Office Action dated 4/13/2012 for U.S. A lication No. 10/034,197
`Office Action dated 2/2/2012 for U.S. A lication No. 10/034,197
`FatPi e’s Proosed Modifications to Claim Construction
`
`1013
`1014
`
`O’Neill entitled “ATM Partial Cut-Throuh” “Hodkinson”)
`
`U.S. Patent No. 6,317,431 by Terence G. Hodgkinson and Alan W.
`Adaptive Private Networking Configuration Editor User’s Guide,
`
`APNware Release 2.5 FATPIPE-001374-l448
`
`1017
`1018
`
`Decision, IPR2016-00976, Paper No. 7 (November 2, 2016)
`FatPi e’s Infi‘inement Contentions
`
`8479466571
`
`_iV_
`
`FatPipe Exhibit 2001, pg. 4
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`U.S. Patent No. 6,775,235
`
`Pursuant to 35 U.S.C. §§ 311-319 and 37 C.F.R. §§ 42.100 et seq, Viptela,
`
`Inc. (“Petitioner”) hereby respectfully requests interpartes review of claims 4, 5,
`
`6-15, 19, and 22-24 (“Challenged Claims”) of U.S. Patent No. 6,775,235 (Ex.
`
`1001; “the ’235 Patent”). There exists a reasonable likelihood that Petitioner will
`
`prevail with respect to at least one of the Challenged Claims, which are
`
`unpatentable over the prior art discussed herein.
`
`1.
`
`MANDATORY NOTICES
`
`Pursth to 37 C.F.R. § 42.8, Petitioner provides the following disclosures:
`
`A.
`
`Real Party-ln-lnterest (37 C.F.R. §42.8(b)(1))
`
`Petitioner, Viptela, Inc., located at 1732 North First St., Suite 600, San Jose,
`
`California 95112, is the real party-in-interest for the instant petition.
`
`B.
`
`Related Matters (37 C.F.R. § 42.8(b)(2))
`
`The ’235 Patth is currently involved in a pending lawsuit (the “District
`
`Court Litigation”) involving Petitioner originally captioned It'arPipe, Inc. v.
`
`Viptela, Inc. , United States District Court For the District Of Delaware, Case No.
`
`1:16-CV-182. (EX. 1008.)
`
`FatPipe, Inc. is also asserting U.S. Patent No. 7,406,048 (Ex. 1003; “the
`
`’048 Patent”) in the District Court Litigation against Petitioner. A separate IPR
`
`petition has been filed by Petitioner with respect to the ’048 Patent. Petitioner
`
`FatPipe Exhibit 2001, pg. 5
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`US. Patent No. 6,775,235
`
`requests that both Petitions be assigned to the same Board for administrative
`
`efficiency, as that patent is directed generally to the same subject matter.
`
`The ‘235 Patent is also subject to a separate proceeding before the Board in
`
`lPR2016-00976, filed by Talari Networks, Inc. (the “’976 IPR”). See Petition for
`
`Inter Perrier Review, IPR2016-00976, Paper No. 1 (April 29, 2016) (EX. 1010).
`
`The Board recently instituted proceedings on claims 4, 5, 7-15, and 19 in the ’976
`
`IPR. See Decision, IPR2016-00976, Paper No. 7 (November 2, 2016) (Ex. 1017).
`
`This Petition is substantially identical to the Petition in the “976 IPR.l
`
`Lead and Backup Counsel (37 C.F.R. §42.8(b)(3) and 42.10(a))
`C.
`
`
`
`
`Lead Counsel:
`Robert C. Hilton (Reg. No. 47,649)
`
`Backup Counsel:
`George B. Davis (Reg. No. 68,205)
`
`Email: rhilton@mcguirewoods.com Email: gdavis@mcguirewoods.com
`
`Postal/Hand Delivery Address:
`MCGUIREWOODS LLP
`
`Postal/Hand Delivery Address:
`MCGUIREWOODS LLP
`
`2000 McKinney Ave, Suite 1400
`Dallas, TX 75201
`
`Tel.: (214) 932-6400
`Fax; (214) 932-6499
`
`Gateway Plaza
`800 East Canal Street
`
`Richmond, VA 23219
`
`Tel.: (804) 775—1000
`Fax.: (804) 775—2016
`
`1 In addition to the claims under review in the ’976 IPR, this Petition also
`
`challenges claims 6 and 22-24 of the ’235 Patent.
`
`FatPipe Exhibit 2001, pg. 6
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`US. Patent No. 6,775,235
`
`D.
`
`Service Information (37 C.F.R. § 42.8(b)(4))
`
`Service on Petitioner may be made by email, mail or hand delivery at the
`
`addresses shown above.
`
`E.
`
`Payment of Fees (37 C.F.R. §§ 42.15(a) and 42.103(a))
`
`The Office is authorized to charge the fees specified by 37 C.F.R.
`
`§§ 42.103(a) and 42.15(a) to Deposit Account No. 231951 as well as any
`
`additional fees that might be due in connection with this Petition.
`
`F.
`
`Standing (37 C.F.R. § 42.104(a))
`
`Petitioner certifies that the patent sought for review is eligible for inter
`
`partes review and that Petitioner is not barred or estopped from requesting an inter
`
`partes review challenging the patent claims on the grounds identified herein.
`
`II.
`
`OVERVIEW OF CHALLENGE AND RELIEF REQUESTED
`
`Pursuant to C.F.R. § 42.10403), Petitioner requests interpartes review of the
`
`Challenged Claims on the grounds set forth below and requests that they be found
`
`unpatentable. Additional support for each ground is set forth in the Declaration of
`
`Dr. Leonard Forys (Ex. 1005).
`
`A.
`
`Publications Relied Upon
`
`Exhibit 1006 — US. Patent No. 6,628,617 to Karol et al. (“Karol”) filed on
`
`March 3, 1999 and issued on September 30, 2003. Karol is prior art under at least
`
`35 use. § 102(e).
`
`FatPipe Exhibit 2001, pg. 7
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`US. Patent No. 6,775,235
`
`Exhibit 1011 — Data and Computer Communications by William Stallings,
`
`Prentice-Hall, 5th Edition, 1997, ISBN-81-203-l240-6, (“Stallings”). Stallings is
`
`prior art under at least 35 U.S.C. § 102(b) because it was published in 1997. (Ex.
`
`1011 at inside cover page.)
`
`B.
`
`Grounds For Challenge
`
`Petitioner requests cancellation of the Challenged Claims on the following
`
`grounds:
`
`(i)
`
`Claims 4-11, 14, 19, and 22-24 are anticipated under 35 U.S.C. § 102
`
`by Karol.
`
`(ii)
`
`Claims 5, 6, 11-15, 19, and 22—24 are obvious under 35 U.S.C. § 103
`
`based on Karol (Ex. 1006) in view of Stallings.
`
`(iii) Claims 4-15, 19, and 22-24 are obvious under 35 U.S.C. § 103 based
`
`on Karol.
`
`III. RELEVANT INFORMATION CONCERNING THE CONTESTED
`
`PATENT
`
`A.
`
`Effective Filing Date of the ’235 Patent
`
`The ’235 Patent references two provisional applications. Provisional
`
`application No. 60/2 59,269 was filed on December 29, 2000, and Provisional
`
`application No. 60/355,509 was filed on February 8, 2002. All of the asserted prior
`
`art precedes the earliest possible priority date — December 29, 2000.
`
`FatPipe Exhibit 2001, pg. 8
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`US. Patent No. 6,775,235
`
`B.
`
`The ’235 Patent (Ex. 1001)
`
`1.
`
`Overview of the ’235 Patent
`
`The ’235 Patent is directed “to computer network data transmission, and
`
`more particularly relates to tools and techniques for communications using
`
`disparate parallel networks...” (Ex. 1001 at 1:17-24, 1:56-60, 2:19-26.) The ’235
`
`Patent teaches that it was well known in the prior art to: have a frame relay
`
`network configured in parallel with a disparate VPN or other Internet-based
`
`network (see, e.g_, Ex. 1001 at 5:24-27); use a disparate network for
`
`reliability/redundancy (see, e.g., Ex. 1001 at 4:25-27 and FIG. 5); use a disparate
`
`network for load-balancing (see, e.g., Ex. 1001 at 9:4-9); and that secure routing
`
`paths were used to route to “Internet-based communication solutions such as VPNs
`
`and Secure Sockets Layer (SSL).” (See, cg, EX. 1001 at 4:5-10; see also Ex. 1005
`
`at W 47, 50-53, 59-61, 116-121.)
`
`2.
`
`Prosecution History
`
`The application leading to the ’235 Patent was filed on February 7, 2003,
`
`and is a continuation-in-part of application number 10/034,l97 filed on
`
`December 28, 2001 (“the ’197 Application”). (Ex. 1001 at cover.) During
`
`prosecution of the application leading to the ’235 Patent, the first Office Action
`
`mailed February 25, 2004 rejected claims 1-4, 8-10, 23-26, 28, 29, and 32 as
`
`invalid over US. Patent No. 6,016,307 to Kaplan er 51!. (Ex. 1002 at 367-373.) The
`
`FatPipe Exhibit 2001, pg. 9
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`US. Patent No. 6,775,235
`
`Examiner allowed claims 11-22, 30, 31, and 33-35 which recited “per-packet
`
`selection” and/or “accessing the multiple parallel disparate networks using at least
`
`two known location address ranges.” (Ex. 1002 at 373—377.) The rejected claims
`
`were canceled, and the remaining allowed claims were accepted. (Ex. 1002 at 384-
`
`392; see also, Ex. 1004.)
`
`C.
`
`Claim Construction
`
`1.
`
`Level of Ordinary Skill in the Art
`
`A person of ordinary skill in the art at the time of the filing date of the ’235
`
`Patent (“POSITA”) would have had at least a Bachelor of Science in Computer
`
`Science, Computer Engineering, Electrical Engineering, or an equivalent field as
`
`well as at least two years of academic or industry experience in any type of
`
`networking field. (Ex. 1005 at 1] 31.)
`
`2.
`
`Patent Owner’s Proposed Constructions
`
`Petitioner submits that no construction is necessary and that all claim terms
`
`of the ’235 Patth should be given their ordinary and customary meaning, as
`
`understood by a POSITA in the context of the entire disclosure. See In re
`
`Tmnslogic Tech, Inc, 504 F.3d 1249, 1257 (Fed. Cir. 2007). Petitioner does not
`
`concede that any Challenged Claim meets statutory standards for patent claiming.
`
`In the co-pending case ofFatpzpe, Inc. v. Talari Networks, Inc, 5:16—CV—54—BO
`
`(E.D.N.C.), PO proposed the following constructions (Ex. 1014):
`
`FatPipe Exhibit 2001, pg. 10
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`US. Patent No. 6,775,235
`
`
`“Internet based network”
`
`
`
`
`Term
`Patent Owner’s Proposed Construction
`“private network”
`“a communication path that is unavailable to
`
`
`
`the eneral ublic”
`
`
`
`
`“a communication path that is available on
`the ublic Internet”
` “disparate networks”
`
`
`“networks that are different in kind, eg. a
`private network and an Internet based
`
`
`
`
`networ ”
`
`
`racket basis”
`acket by packet”
`
`
`
`“packet path selector”
`
`“repeated instances of the
`selecting step make network
`ath selections”
`
`“module(s) that selects which path to send a
`iven acket on”
`
`“more than one occurrence of selecting a
`network path”
`
`
`
`
`
`
`
`
`
`
`“parallel network”
`
`“Session”
`
`
`
`
`“at least two networks configured to allow
`altemate data paths”
`“an active communications connection,
`measured from beginning to end, between
`
`computers or applications over a network”
`
`
`
`
`For this IPR, Petitioner submits that none of these terms need construction.
`
`To the extent the Board determines that any of these terms require construction for
`
`purposes of this IPR, a POSITA would understand PO’s constructions to be within
`
`the broadest reasonable interpretation. (See, e.g., Ex. 1005 at W 72-81.) See
`
`Amazon.com, Inc. v. Barnesandnobie.com, Inc, 239 F.3d 1343, 1351 (Fed. Cir.
`
`2001) (“A patent may not, like a ‘nose of wax,’ be twisted one way to avoid
`
`anticipation and another to find infringement”). Any interpretation of claim terms
`
`here is not binding upon Petitioner in any litigation related to the ’235 Patent. See
`
`In re Z/etz, 13 USPQ2d 1320, I322 (Fed. Cir. 1989).
`
`FatPipe Exhibit 2001, pg. 11
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`U.S. Patent No. 6,775,235
`
`IV.
`
`SUMMARY OF PRIOR ART AND REFERENCES RELIED ON
`
`None of the prior art discussed below was considered by the Patent Office
`
`during prosecution of the ’235 Patent. These prior art references are directed to the
`
`same field as the ’235 Patent (data networking) and operate using the same
`
`architecture as the ’235 Patent (routing to parallel disparate networks). (Ex. 1005 at
`
`W 84, 86, 87.) No secondary considerations support a finding of nonobviousness.
`
`A.
`
`Brief Summary of Karol (Ex. 1006)
`
`Karol is prior art under at least 35 U.S.C. § 102(e). (See supra at § II(A).)
`
`Karol is directed towards parallel “internetworking of connectionless (rag. Internet
`
`Protocol or “IP”) and connection oriented (cg, ATM, MPLS, RSVP) networks.”
`
`(See, e.g., EX. 1006 at 1:7-14, 1:19-20, Fig. 1; Ex. 1005 at W 85-89, 91.)
`
`To route data between the connection oriented and connectionless networks,
`
`Karol discloses a “gateway” that can operate in either serial or parallel modes. (Ex.
`
`1006 at 3:58-66; Ex. 1005 at 1] 91.) The gateway can make a routing selection
`
`between the connection oriented or connectionless network based on specific
`
`criteria, such as “maximizing efficiency.” (Ex. 1006 at 3:58-66; Ex. 1005 at 11 87.)
`
`For routing, Karol discloses routing tables in databases:
`
`the CL network uses the
`
`forwarding database, and the CO network uses the flow database. (See, e.g., Ex.
`
`1006 at 7:31—54 and FIG. 4; Ex. 1005 at 1H] 95-99.)
`
`FatPipe Exhibit 2001, pg. 12
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`US. Patent No. 6,775,235
`
`B.
`
`Brief Summary of Stallings (Ex. 1011)
`
`Stallings is prior art under at least 35 U.S.C. § 102(b). (See supra at § II(A).)
`
`Stallings describes “ATM,” “Frame Relay,” “Packet Switching (Routing),”
`
`“Network Security,” frame relay, IP protocol, among other data and computer
`
`communications topics. (See, e.g., Ex. 101 1 at 24-26; Ex. 1005 at 1111 129-141.)
`
`V.
`
`A REASONABLE LIKELIHOOD EXISTS THAT THE
`
`CHALLENGED CLAIMS ARE UNPATENTABLE
`
`A.
`
`Ground 1: Claims 4-11, 14, 19, and 22-24 of the ’235 Patent (Ex.
`
`1001) are anticipated by Karol (EX. 1006)
`
`Claim 4[a]: “A controller which controls access to multiple networks in a
`parallel network configuration, suitable networks comprising Internet-based
`networks andprivate networks from at least one more provider, in combination,
`the controller comprising: ”
`
`Karol discloses “A controller” which controls access to multiple networks in
`
`a parallel configuration:
`
`the “CL—CO gateway” alone or in combination with one
`
`or more routers and/or switches controls access to either a “connectionless” (or
`
`“CL”) network data path or to a “connection oriented” (or “CO”) network data
`
`path that are configured in parallel. (See Ex. 1006 at 1:7-16, Fig. 1; Ex. 1005 at 111]
`
`157-160.) “The CL network is typically, although not necessarily, an IP network.”
`
`(EX. 1006 at 2:58-59; EX. 1005 at 11 157.) In parallel with the CL network, the CO
`
`network is a private network that “can be an MPLS ...” or “telephony network...”
`
`(Ex. 1006 at 2:52-58; EX. 1005 at 1] 157.) PO has identified MPLS as a private,
`
`parallel, disparate network. (Ex. 1018 at Appendix I at p. 44; and Ex. 1005 at 1111
`
`9
`
`FatPipe Exhibit 2001, pg. 13
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`US. Patent No. 6,775,235
`
`161-162.) Karol discloses the CL-CO “parallel contrgrarz‘on could occur, for
`
`example, if two service providers, one with an IP-router-based network and the
`
`other with a CO-switch—based network, offer enterprises ‘long-distance’
`
`connectivity...” (emphasis added) (Ex. 1006 at 3:47—51; Ex. 1005 atfll 159.)
`
`Thus, Karol discloses a “controller” (e.g., either of the CL-CO gateway or
`
`the combination of the CL-CO gateway with one or more routers and/or switches)
`
`that “controls access to multiple networks in a parallel network configuration in
`
`combination” (cg, the CL or CO network) and multiple networks are chosen from
`
`“suitable networks comprising lntemet-based networks and private networks from
`
`at least one more provider” (e. g., the CL path is based on Internet protocol service
`
`from a first service provider and the CO path is based on ATM or MPLS protocol
`
`service from a second service provider). (Ex. 1005 at 11 160 and 1111 161-163.)
`
`Claim 4[b]: “a site interface connecting the controller to a site; ”
`
`Considering the “controller” to be the CL-CO gateway alone, then the “site”
`
`in Karol is either the routers/switches connected to the CL—CO gateway and/or the
`
`source 101 and/or destination 151 endpoints. (Ex. 1005 at '11 175; Ex. 1006 at 3:44-
`
`51, 4:36-44, 4:65-67, and Fig. 1.) The “site interface” in Karol is one or more of
`
`the input line cards 40] or a network connection — shown in Fig. 1 as an
`
`“interface” between source 101 and node 1 11. (Ex. 1005 at 1111 172-176; EX. 1006
`
`at 3:44-51, 4:36-44, 4:65-67, 6:44-50 and Figs. 1 and 4.)
`
`10
`
`FatPipe Exhibit 2001, pg. 14
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`US. Patent No. 6,775,235
`
`Considering the “controller” to be the CL-CO gateway in combination with
`
`one or more routers and/or switches, then the “site” in Karol is the source 101
`
`and/or destination 151 endpoints. (Ex. 1005 at 11 175; Ex. 1006 at 3:44—51, 4:36-44,
`
`4:65—67, and Fig. 1.) The “site interface” is a network connection. (Ex. 1005 at W
`
`172-176; EX. 1006 at 3:44-51, 4:36-44, 4:65-67, 6:44-50 and Figs. 1 and 4.)
`
`Claim 4[c|: “at least two network interfaces which send pockets toward the
`networks; am ”
`
`Karol discloses that at least two “output line cards 402” are utilized to
`
`“receive datagrams from either of” the “CO switch 410 or CL router/switch 420”
`
`and then “direct them to external networks” as further illustrated in and described
`
`with respect to FIG. 4 of Karol. (See, eg. EX. 1005 at 1111 96-99, 173, 177; EX. 1006
`
`at 3:58-66, 4:45-65, 6:44—50, Figs.
`
`1 and 4.) FIG. 4 discloses at least two such
`
`“output line cards” that send packets over network interfaces to the two respective
`
`CL and CO networks. (Ex. 1006 at 4:36-67, FIG. 1, and FIG. 4; EX. 1005 at 11 178.)
`
`Alternatively, the combination of the CL-CO gateway and one or more routers
`
`and/or switches shown in FIG. 1 also depicts at least two “network interfaces” to
`
`both of the CL network and the CO network that are depicted as exemplary router
`
`“node 121” and exemplary CO switching element “node 161 .” (Ex. 1006 at 3:5 8-
`
`66, 4:45-65, and FIG. 1; Ex. 1005 at 1111 158, 179.)
`
`Thus, Karol discloses a “controller” (eg, the CL-CO gateway) with at least
`
`two “network interfaces” (eg, the output line cards coupling the CL router to the
`
`11
`
`FatPipe Exhibit 2001, pg. 15
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`US. Patent No. 6,775,235
`
`CL network and the CO switch to the CO network), which “send packets toward”
`
`the “networks” (eg, the CL and CO networks). Alternatively, Karol discloses a
`
`“controller” (eg, the CL-CO gateway in combination with one or more routers
`
`and/or switches) having at least two “network interfaces” (eg, the network
`
`connections to respective CL and CO networks), which “send packets toward” the
`
`“networks” (e.g, the CL and CO networks). (EX. 1005 at 1111 180-181.)
`
`Claim 4[d]: “a packet path selector which selects between network interfaces on
`a per-packet basis according to at least: a destination ofthe packet, an optional
`presence ofalternate paths to that destination, and at least one specifier! criterion
`for selecting between alternate paths when such alternate paths are present; ”
`
`Karol discloses a “packet path selector” including at least a “gateway
`
`processor,” a “CL router/switch,” a “CO switch,” a “packet buffer,” a “protocol
`
`converter,” and one or more “input line cards” that together determine if a
`
`particular packet (or “datagram,” which is a term used by Karol interchangeably
`
`with the term “packet” (e.g., Ex. 1006 at 5233-25)) from a “source endpoint”
`
`should be forwarded to either the CL or CO network based on multiple criteria
`
`including whether the CO network has a valid connection for the particular packet
`
`as further illustrated in and described with respect to Figure 4 of Karol. (EX. 1005
`
`at 1111 96-99, 183-189; Ex. 1006 at 6:31-50 and FIG. 4.)
`
`The “packet-path” selector of Karol selects between network interfaces
`
`associated with a C0 and CL network on a per packet basis: “datagrams received
`
`in input line cards 401 can be directed either to CO switch 410 or CL router/switch
`
`12
`
`FatPipe Exhibit 2001, pg. 16
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`US. Patent No. 6,775,235
`
`420” so that “output line cards 402 can receive datagrams from either of the last
`
`mentioned elements and direct them to external networks.” (Ex. 1005 at W 96-99;
`
`184—185; Ex. 1006 at 6:44—50 and FIG. 4.) To route the packets to a destination of
`
`the packet, Karol discloses a “fmwarding database 432” within the gateway
`
`processor to determine if a particular packet matches a combination of
`
`“Destination IP address; Next hop router; Outgoing port (interface)” that would
`
`cause such a packet to be routed to the CL network or to be considered for routing
`
`over the CO network. (Ex. 1006 at 7:36-41; Ex. 1005 at 1] 185.)
`
`For packets that are candidates for the CO network, Karol also discloses that
`
`each such packet is compared at the gateway processor with the “flow database
`
`433” to determine if a particular packet matches a desired combination of “(a) an
`
`outgoing port field, which indicates the port on which a datagram whose entries
`
`match a particular record’s entries is forwarded; (b) if the outgoing port is
`
`‘invalid,’ the next field ‘forward or hold’[] entry indicates whether packet should
`
`be forwarded or held in packet buffer 440; (c) destination address; (d) source
`
`address; (e) source port; (f) destination port; (g) type of service; (h) protocol field;
`
`(i) TCP Flags; (i) outgoing port; (k) forward or hold flag, and (1) a mask which
`
`indicates which of the data entries is applicable to the particular record” in order to
`
`route such a packet to the CO network instead of the CL network depending on
`
`13
`
`FatPipe Exhibit 2001, pg. 17
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`US. Patent No. 6,775,235
`
`availability of a valid connection in the CO network for a flow associated with the
`
`particular packet. (Ex. 1006 at 7:42-54, 7:60-82; Ex. 1005 at 1111 186, 187.)
`
`Karol discloses routing selections between the CL and CO networks are
`
`based at least upon “bandwidth availability” that can be “dynamically allocated to
`
`flows on an as-needed basis” and can “divert[] connections away from congested
`
`links.” (Ex. 1006 at 17:18-26 and 17:63-18:2; EX. 1005 atfl 188.)
`
`Thus, Karol discloses a “packet path selector” (e.g., the structural elements
`
`depicted in FIG. 4 of Ex. 1005 at 1] 184) that “selects between network interfaces
`
`on a per-packet basis” (e.g., packet path selector compares information in each
`
`packet received at the CL-CO gateway to determine if the packet will be routed to
`
`the CL or CO network interface output line card) according to at least “a
`
`destination of the packet” (e.g., gateway processor in the CL-CO gateway
`
`compares the destination address of each received packet to fields in both the
`
`forwarding and flow databases), “an optional presence of alternate paths to that
`
`destination” (eg, the gateway processor will only forward a particular packet to
`
`the CO network when a valid connection exists for the flow associated with the
`
`particular packet), and “at least one specified criterion for selecting between
`
`alternate paths when such alternate paths are present” (8.32, based upon the needs
`
`of a particular flow or to avoid congested links). (Ex. 1005 at 1111 189-191.)
`
`14
`
`FatPipe Exhibit 2001, pg. 18
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`US. Patent No. 6,775,235
`
`Claim 41c]: “wherein the controller receives a packet through the site interface
`and sends the packet through the network interface that was selected by the
`packet path selector. ”
`
`If the “controller” is the CL-CO gateway alone, Karol discloses that the CL-
`
`CO gateway receives packets through the “site interface” which is the “input line
`
`cards 401” and the packets “can be directed either to CO switch 410 or CL
`
`router/switch 420” to send the packets through the “network interface,” which are
`
`the “output line cards 402 [that] can receive datagrams from either of the last
`
`mentioned elements and direct them to external networks.” (Ex. 1005 at 1111 96-99,
`
`200; EX. 1006 at 6:44-50 and FIG. 4.) If the “controller” is the CL-CO gateway in
`
`combination with one or more routers and switches, then the “controller” receives
`
`packets through the “network connection,” and as described above, the packets are
`
`routed to the network interface (such as node 121 or 16]). (1d,) Figure 5 discloses
`
`an exemplary process for determining the network path selection and actual
`
`forwarding to the CL or CO network interface. (Ex. 1005 at 1111 100-103, 200, 201;
`
`Ex. 1006 at 8:56—9:36 and FIG. 5 and 6.) Thus, Karol’s packet path selector (cg,
`
`depicted in FIG. 4) compares information in each packet received at the CL—CO
`
`gateway and then routes each packet either to the CL network interface output line
`
`card or to the CO network interface output line card according to the process
`
`described in FIG. 5. (Ex. 1005 at 1111 200-202.)
`
`Claim 51a]: “A methodfor combining connectionsfor access to multiple
`parallel disparate networks, the method comprising the steps of: ”
`
`15
`
`FatPipe Exhibit 2001, pg. 19
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`US. Patent No. 6,775,235
`
`For the reasons noted in § V(A) at claim element 4[a], claim 5[a] is
`
`anticipated, and Karol discloses that the CO and CL networks are disparate in that
`
`the CL and CO networks are “two different, parallel routes” comprising, for
`
`example, an IP network in parallel with a MPLS or ATM network. (Ex. 1006 at
`
`4:40—44; Ex. 1005 at w 207, 208; see also EX. 1005 at W 85-99, 206-212.)
`
`Claim 5[b|: “obtaining at least two known location address ranges which have
`associated networks; ”
`
`Karol discloses this element through the use of routing tables that contain
`
`location addresses. For example, Karol discloses with respect to the CL network
`
`that the “datagram forwarding database 432” is “the database used in typical CL IP
`
`routers” that “stores the next hog router address and outgoing port number
`
`
`corresponding to each destination address” and thus the “fields in each record in
`
`this database would be: Destination IP address; Next hog router; Outgoing port
`
`(interface).” (emphasis added) (Ex. 1006 at 7:36-41; Ex. 1005 at 1} 97, 224.) The
`
`flow database 433 provides the same function for the CO network. (EX. 1006 at
`
`7:42-54; Ex. 1005 at w 98, 225.)
`
`Karol also discloses methodologies for obtaining the routing table
`
`information, which include the location address ranges associated with the CL and
`
`CO network paths as shown above, such as “the network grovtder can set user-
`
`s eci ic routin r tables at the CL-CO atewa s” SO that “the user-sgecific routing
`
`then determines which users’ flows are sent to the (70 network” versus those that
`
`16
`
`FatPipe Exhibit 2001, pg. 20
`Viptela v. FatPipe
`|PR2017-01125
`
`

`

`Petition for Inter Partes Review
`
`US. Patent No. 6,775,235
`
`are routed to the CL network. (emphasis added) (EX. 1006 at 16:3-9; EX. 1005 at 111]
`
`108-1 12, 226.) Karol also discloses obtaining “updates” to such routing tables. (EX.
`
`1006 at 13:6—16, FIG. 8; Ex. 1005 at 1111 108-1 12, 226.)
`
`Thus, Karol discloses “at least two known location address ranges” (e.g, the
`
`addresses stored in the routing t