Prosecution Insights
Last updated: November 20, 2026
Application No. 19/265,598

METHOD AND SYSTEM FOR FACILITATING MULTI-TENANCY ROUTING IN VIRTUAL PRIVATE CLOUD

Non-Final OA §103§112§DOUBLEPATENT
Filed
Jul 10, 2025
Priority
Dec 19, 2023 — IN 202341086726 +1 more
Examiner
JEAN GILLES, JUDE
Art Unit
2459
Tech Center
2400 — Computer Networks
Assignee
Nutanix Inc.
OA Round
1 (Non-Final)
93%
Grant Probability
Favorable
1-2
OA Rounds
1y 0m
Est. Remaining
95%
With Interview

Examiner Intelligence

Grants 93% — above average
93%
Career Allowance Rate
885 granted / 953 resolved
+34.9% vs TC avg
Minimal +2% lift
Without
With
+2.5%
Interview Lift
resolved cases with interview
Typical timeline
2y 4m
Avg Prosecution
17 currently pending
Career history
976
Total Applications
across all art units

Statute-Specific Performance

§101
13.2%
-26.8% vs TC avg
§103
33.8%
-6.2% vs TC avg
§102
19.3%
-20.7% vs TC avg
§112
4.7%
-35.3% vs TC avg
Black line = Tech Center average estimate • Based on career data from 953 resolved cases

Office Action

§103 §112 §DOUBLEPATENT
Notice of Pre-AIA or AIA Status The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . This communication is in reply to 07/10/2025. Claimed priority is granted from Foreign Application NumberIN202341086726, filed on 12/19/2023. Information Disclosure Statement The information disclosure statement (IDS) submitted on 07/10/2025 was filed in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner. Claim Rejections - 35 USC § 103 The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action: A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. Claims 1-8, 10-17 and 19-20 are rejected under 35 U.S.C. 103 as being unpatentable over Hines et al., US 20090154463 A1, in view of Anupkumar T, US 20190238457 A1, hereinafter (Kumar). Regarding claim 1, the combination of Hines and Kumar teaches the invention as claimed. 1. A method for facilitating isolation of routes in a network, the method comprising: receiving, by a computing system in the network, subscription information indicating that a first subset of the network subscribes to a first border gateway protocol (BGP) community (Kumar, 0004, 0027, 0033; Fig 1: peer communicate RT subscription identifying desired communities, filters are maintained per peer), wherein subscription to a respective BGP community indicates that a subscriber is to receive routes associated with the BGP community (Hines, 0057-0058, 0064; Fig. 2: PE routers receive and exchange routes through BGP/MP-BGP); receiving, from a routing protocol instance of the network, a first route advertisement indicating a first route in the network, wherein the first route advertisement comprises a BGP community field with a value equivalent to a value of first BGP community (Hines, 0046, 0064, supplies tagged routes; Kumar, 0021 identifies their RT extended-community representation); determining, based on the BGP community value in the route advertisement, that the first subset of the network subscribes to the first route tag (Hines, 0046, 0064 checks received RTs against import configuration; Kumar, 0027 supplies explicit subscription-based matching); and providing the first route to the first subset of the network (Hines, 0058, 0060; Kumar, 0027). It would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to implement Hines’ configured route distribution using Kumar’s expressly communicated subscriptions and per-peer filters. Both select recipients using the same RT identifier. This provides a concrete mechanism for updating recipient interests while reducing unnecessary advertisements and rout8ing work- the benefits stated in Kumar, 0029-0030. Matching the existing RT identifiers provides a reasonable expectation of success. By this rationale, claim 1 is rejected. Likewise, regarding claims 2-8, 10-17 and 19-20 the combination Hines-Kumar teaches: 2. The method of claim 1, wherein the routing protocol instance executes in a transit router that facilitates exchange of routing information among a plurality of subsets of the network (Hines, 0057-0064; fig. 2: supplies intermediary PE routers exchanging routing information between customer networks. This supports “transit router” by its recited function). 3. The method of claim 1, further comprising configuring the routing protocol instance to distribute the first route with the first BGP community value (Hines, 0076-0078). 4. The method of claim 1, further comprising: storing the subscription information associated with the first BGP community value in a data structure; and in response to receiving the first route advertisement, looking up the BGP community value in the data structure to determine that the first subset of the network subscribes to the first BGP community (Kumar, 0033, 0035 and Hines, 0064). 5. The method of claim 1, further comprising configuring a forwarding path for the first subset of the network to allow traffic to and from the first subset of the network via the first route (Hines, 0059-0060). 6. The method of claim 1, wherein the subscription information further indicates that the first subset of the network subscribes to a second BGP community, wherein the second BGP community comprises routes associated with a set of shared services (Hines, 0048-0049, 0078; figs 1 and 5). 7. The method of claim 6, further comprising: receiving a second route advertisement indicating a second route in the network, wherein the second route advertisement comprises a value of the second BGP community; determining that the first subset of the network subscribes to the second BGP community; and providing the second route to the first subset of the network (Hines, 0060 and 0079; figs. 2 and 6). 8. The method of claim 1, further comprising precluding the first subset of the network from receiving route advertisements associated with BGP communities to which the first subset of the network does not subscribe (Kumar, 0004 and 0027). 10. A non-transitory computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for facilitating isolation of routes in a network (Kumar, 0006, and 0031), the method comprising: receiving subscription information indicating that a first subset of the network subscribes to a first border gateway protocol (BGP) community (Kumar, 0004, 0027, 0033; Fig 1: peer communicate RT subscription identifying desired communities, filters are maintained per peer), wherein subscription to a respective BGP community indicates that a subscriber is to receive routes associated with the BGP community (Hines, 0057-0058, 0064; Fig. 2: PE routers receive and exchange routes through BGP/MP-BGP); receiving, from a routing protocol instance of the network, a first route advertisement indicating a first route in the network, wherein the first route advertisement comprises a BGP community field with a value equivalent to a value of first BGP community (Hines, 0046, 0064, supplies tagged routes; Kumar, 0021 identifies their RT extended-community representation); determining, based on the BGP community value in the route advertisement, that the first subset of the network subscribes to the first route tag (Hines, 0046, 0064 checks received RTs against import configuration; Kumar, 0027 supplies explicit subscription-based matching); and providing the first route to the first subset of the network (Hines, 0058, 0060; Kumar, 0027). 11. The non-transitory computer-readable storage medium of the non-transitory computer-readable storage medium of wherein the routing protocol instance executes in a transit router that facilitates exchange of routing information among a plurality of subsets of the network (Hines, 0057-0064; fig. 2: supplies intermediary PE routers exchanging routing information between customer networks. This supports “transit router” by its recited function). 12. The non-transitory computer-readable storage medium of the non-transitory computer-readable storage medium of wherein the method further comprises configuring the routing protocol instance to distribute the first route with the first BGP community value (Hines, 0076-0078). 13. The non-transitory computer-readable storage medium of The non-transitory computer-readable storage medium of wherein the method further comprises: storing the subscription information associated with the first BGP community value in a data structure; and in response to receiving the first route advertisement, looking up the BGP community value in the data structure to determine that the first subset of the network subscribes to the first BGP community (Kumar, 0033, 0035 and Hines, 0064). 14. The non-transitory computer-readable storage medium of the non-transitory computer-readable storage medium of wherein the method further comprises configuring a forwarding path for the first subset of the network to allow traffic to and from the first subset of the network via the first route (Hines, 0059-0060). 15. The non-transitory computer-readable storage medium of the non-transitory computer-readable storage medium of wherein the subscription information further indicates that the first subset of the network subscribes to a second BGP community, wherein the second BGP community comprises routes associated with a set of shared services (Hines, 0048-0049, 0078; figs 1 and 5). 16. The non-transitory computer-readable storage medium of the non-transitory computer-readable storage medium of wherein the method further comprises: receiving a second route advertisement indicating a second route in the network, wherein the second route advertisement comprises a value of the second BGP community; determining that the first subset of the network subscribes to the second BGP community; and providing the second route to the first subset of the network (Hines, 0060 and 0079; figs. 2 and 6). 17. The non-transitory computer-readable storage medium of the non-transitory computer-readable storage medium of wherein the method further comprises precluding the first subset of the network from receiving route advertisements associated with BGP communities to which the first subset of the network does not subscribe (Kumar, 0004 and 0027). 19. A computing system, comprising: a processor; and a memory coupled to the processor and storing instructions, which when executed by the processor cause the processor to perform a method for facilitating isolation of routes in a network (Kumar, 0006, and 0031), the method comprising: receiving subscription information indicating that a first subset of the network subscribes to a first border gateway protocol (BGP) community (Kumar, 0004, 0027, 0033; Fig 1: peer communicate RT subscription identifying desired communities, filters are maintained per peer), wherein subscription to a respective BGP community indicates that a subscriber is to receive routes associated with the BGP community (Hines, 0057-0058, 0064; Fig. 2: PE routers receive and exchange routes through BGP/MP-BGP); receiving, from a routing protocol instance of the network, a first route advertisement indicating a first route in the network, wherein the first route advertisement comprises a BGP community field with a value equivalent to a value of first BGP community (Hines, 0046, 0064, supplies tagged routes; Kumar, 0021 identifies their RT extended-community representation); determining, based on the BGP community value in the route advertisement, that the first subset of the network subscribes to the first route tag (Hines, 0046, 0064 checks received RTs against import configuration; Kumar, 0027 supplies explicit subscription-based matching); and providing the first route to the first subset of the network (Hines, 0058, 0060; Kumar, 0027). 20. The computing system of claim 19, wherein the subscription information further indicates that the first subset of the network subscribes to a second BGP community, wherein the second BGP community comprises routes associated with a set of shared services (Hines, 0048-0049, 0078; figs 1 and 5). Claims 9 and 18 are rejected under 35 U.S.C. 103 as being unpatentable over Hines and Kumar as applied to claims 1 and 10 above, and further in view of Liu et al., US 20140230044 A1. Regarding claim 9, the combination Hines-Kumar teaches the invention substantially as claimed. They disclose the teaching of claim 1, and 10 respectively, but fail to disclose a method/system wherein the first subset of the network is a virtual private cloud. This feature is well-known in the art as evidenced by Liu. In the same field of endeavor, Liu teaches configuring an RT-based VPN instance and binds a VPC to it (Liu 0086-0089, and 0092; Fig. 2). Liu’s VPV-to-VPN binding supplies a concrete cloud-network subscriber for the existing RT subscription mechanism. The modification preserves community-based distribution while allowing an authenticated VPC to obtain the subscribed VPN routes. No claim requires more than three prior-art references. By this rationale, claim 18 is rejected. 18. The non-transitory computer-readable storage medium of the non-transitory computer-readable storage medium of wherein the first subset of the network is a virtual private cloud (Liu 0086-0089, and 0092; Fig. 2). The same motivation/reason to combine used for the rejection of claim 9 is also valid for this claim. Double Patenting The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969). A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b). The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13. The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer. Claims 1-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-20 of U.S. Patent No. 12375394 B2. Although the claims at issue are not identical, they are not patentably distinct from each other because: Present Claims Patent Claims Comments 1 and 9 1 and 9 Subscription, tagged advertisement, recipient determination, delivery, and BGP-community implementation 2-8 2-8 Together with its BGP-community limitation in 9 10 and 18 10 and 18 Same 11-17 11-17, together with 18 Together with 18 19-20 19-20 Applying the BGP-community implementation expressly claimed in 9 and 18 Rationale: The present claims largely replace “route tag” with its expressly claimed BGP-community implementation and generalize VPC/PBR terminology to network subsets/forwarding paths. The matching field value implements the same community identification. Those differences do not presently establish a distinct routing operation. For claims 2 and 11, the action should expressly explain implementing the parent’s transit routing instance in a router; “transit VPC” and “transit router” are not interchangeable terms. Claim Rejections - 35 USC § 112 The following is a quotation of 35 U.S.C. 112(b): (b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention. The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph: The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention. Claims 1, 10 and 19 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as failing to set forth the subject matter which the inventor or a joint inventor, or for applications subject to pre-AIA 35 U.S.C. 112, the applicant regards as the invention. Claims 1, 10 and 19 introduce “the first route tag” without expressly identifying it as the first BGP community. Applicants need to clarify that relationship. There is an actual uncertainty about whether these are the same identifier; missing literal antecedent wording alone is insufficient. CONCLUSION Any inquiry concerning this communication or earlier communications from the examiner should be directed to Jude Jean-Gilles whose telephone number is 571-272-3914. The examiner can normally be reached on Mon-Fri, from 9:00AM-5:00PM. Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Tonia Dollinger can be reached on 571-272-4170. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /JUDE JEAN GILLES/Primary Examiner, Art Unit 2459 October 31, 2026
Read full office action

Prosecution Timeline

Jul 10, 2025
Application Filed
Nov 04, 2026
Non-Final Rejection mailed — §103, §112, §DOUBLEPATENT (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12803875
SYSTEM AND METHOD OF CLOUD BASED CONGESTION CONTROL FOR VIRTUALIZED BASE STATION
2y 4m to grant Granted Nov 17, 2026
Patent 12776978
TECHNOLOGIES FOR PROTOCOL EXECUTION WITH AGGREGATION AND CACHING
1y 7m to grant Granted Oct 27, 2026
Patent 12750420
MOBILE INTERACTIVE KIOSK METHOD
1y 5m to grant Granted Sep 29, 2026
Patent 12744725
COHERENT INTERNET NETWORK BONDING SYSTEM
1y 11m to grant Granted Sep 22, 2026
Patent 12744741
SERVICE LEVEL AGREEMENT BASED DATA FORWARDING WITH LINK AGGREGATION GROUPING
1y 8m to grant Granted Sep 22, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

1-2
Expected OA Rounds
93%
Grant Probability
95%
With Interview (+2.5%)
2y 4m (~1y 0m remaining)
Median Time to Grant
Low
PTA Risk
Based on 953 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month