IP Library Granted Patent US 12,737,157
Granted Patent B2
US 12,737,157 · App. 19/025,880 · Granted Sep 15, 2026

Interconnection platform for real-time configuration and management of a cloud-based services exchange

Inventors: Parveen Kumar (Fremont, CA); Gagan Maheshwari (Sunnyvale, CA); Jaganathan Jeyapaul (Saratoga, CA); Brian J. Lillie (Los Altos, CA)
Assignee: Equinix, Inc.
G06F8/30G06F8/70G06F9/5072H04L41/00H04L41/0803H04L41/20H04L47/70H04L67/10H04L67/1097H04L67/567
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,737,157
App. No.
19/025,880
Granted
Sep 15, 2026
Kind
B2
Abstract

In one example, a cloud-based services exchange comprises a plurality of interconnection assets configured to connect a customer of the cloud-based services exchange to one or more cloud service providers, the plurality of interconnection assets including a virtual circuit by which the customer accesses a cloud service from the one or more cloud service providers; and an orchestration engine configured to modify the plurality of interconnection assets.

Claims (61)

1 . A system comprising:

one or more network devices; and

one or more computing devices configured to execute an interconnection platform, the interconnection platform configured to:

implement an interface configured to receive a request for network connectivity between a first network and a second network, wherein the second network is associated with a cloud service provider that provides a cloud service;

based on the request:

determine that a port for the first network is valid for the request; and

configure, based on the request and the determination that the port for the first network is valid for the request, the one or more network devices with a virtual private network (VPN) that provides the network connectivity between the first network and the second network.

2 . The system of claim 1 , wherein:

the interconnection platform is configured to implement one or more API services; and

to determine that the port for the first network is valid for the request, the interconnection platform is configured to orchestrate a first API service of the one or more API services to validate the port for the first network.

3 . The system of claim 1 , wherein the interconnection platform is configured to, based on the request:

determine that a port for the second network is valid for the request; and

configure, based on the request and the determination that the port for the second network is valid for the request, the one or more network devices with the VPN.

4 . The system of claim 1 , wherein:

the request specifies a metropolitan area, and

the interconnection platform is configured to, based on the metropolitan area, orchestrate one or more API services to identify the one or more network devices as located in the metropolitan area and configure the one or more network devices with the VPN.

5 . The system of claim 4 , wherein, to orchestrate the one or more API services, the interconnection platform is configured to invoke a metro service of the one or more API services to validate the metropolitan area and to configure, based on an indication from the metro service that the metropolitan area is valid, the one or more network devices with the VPN.

6 . The system of claim 1 , wherein:

the request comprises a first request for network connectivity and an identifier,

the interconnection platform is configured to:

receive a second request that includes the identifier, and

based on the second request including the identifier and indicating acceptance of the request for network connectivity, configure the one or more network devices with the VPN.

7 . The system of claim 6 , wherein:

the first request comprises an HTTP POST request, and

the second request comprises an HTTP PATCH request.

8 . The system of claim 1 , wherein the one or more network devices are distinct from the one or more computing devices.

9 . The system of claim 1 , further comprising:

a cloud exchange that includes the one or more network devices.

10 . The system of claim 1 , wherein the interconnection platform is configured to, based on the request:

configure the one or more network devices to enable a port for the cloud service for communications using the VPN.

11 . The system of claim 1 , wherein the interconnection platform is configured to, based on the request:

configure the one or more network devices to enable the port for the first network for communications using the VPN.

12 . One or more non-transitory computer-readable media comprising instructions that, when executed by processing circuitry, cause the processing circuitry to:

implement an interface configured to receive a request for network connectivity between a first network and a second network, wherein the second network is associated with a cloud service provider that provides a cloud service;

based on the request:

determine that a port for the first network is valid for the request; and

configure, based on the request and the determination that the port for the first network is valid for the request, one or more network devices with a virtual private network (VPN) that provides the network connectivity between the first network and the second network.

13 . The one or more non-transitory computer-readable media of claim 12 , wherein:

the instructions cause the processing circuitry to implement one or more API services; and

to determine that the port for the first network is valid for the request, the instructions cause the processing circuitry to orchestrate a first API service of the one or more API services to validate the port for the first network.

14 . The one or more non-transitory computer-readable media of claim 12 , wherein the instructions cause the processing circuitry to, based on the request:

determine that a port for the second network is valid for the request; and

configure, based on the request and the determination that the port for the second network is valid for the request, the one or more network devices with the VPN.

15 . The one or more non-transitory computer-readable media of claim 12 , wherein:

the request specifies a metropolitan area, and

the instructions cause the processing circuitry to, based on the metropolitan area orchestrate one or more API services to identify the one or more network devices as located in the metropolitan area and configure the one or more network devices with the VPN.

16 . The oen or more non-transitory computer-readable media of claim 12 , wherein:

the request comprises a first request for network connectivity and an identifier,

the instructions cause the processing circuitry to:

receive a second request that includes the identifier, and

based on the second request including the identifier and indicating acceptance of the request for network connectivity, configure the one or more network devices with the VPN.

17 . The one or more non-transitory computer-readable media of claim 16 , wherein:

the first request comprises an HTTP POST request, and

the second request comprises an HTTP PATCH request.

18 . The one or more non-transitory computer-readable media of claim 12 , wherein the one or more network devices do not include the processing circuitry.

19 . The one or more non-transitory computer-readable media of claim 12 , the instructions cause the processing circuitry to, based on the request, configure the one or more network devices to enable a port for the cloud service for communications using the VPN.

20 . A method comprising:

implementing, by an interconnection platform executed by one or more computing devices, an interface configured to receive a request for network connectivity between a first network and a second network, wherein the second network is associated with a cloud service provider that provides a cloud service;

based on the request:

determining that a port for the first network is valid for the request; and

configuring, based on the request and the determination that the port for the first network is valid for the request, one or more network devices with a virtual private network (VPN) that provides the network connectivity between the first network and the second network.

Continuity (11)
Continuation 18607373 · Mar 15, 2024
Continuation 18146331 · Dec 23, 2022
Continuation 17646375 · Dec 29, 2021
Continuation 17007929 · Aug 31, 2020
Continuation 16172501 · Oct 26, 2018
Continuation 15887165 · Feb 2, 2018
Continuation 15395101 · Dec 30, 2016
Continuation 14927451 · Oct 29, 2015
Provisional Application 62233933 · Sep 28, 2015
Provisional Application 62072976 · Oct 30, 2014
Related Publication 20250156156A1 · May 15, 2025
References Cited (188)
US 6778651B1 · Jost et al. · 2004 [cited by applicant]
US 7526734B2 · Vasilev et al. · 2009 [cited by applicant]
US 7606868B1 · Le et al. · 2009 [cited by applicant]
US 7697558B2 · Pilon et al. · 2010 [cited by applicant]
US 7904882B2 · Hinks · 2011 [cited by applicant]
US 8046440B2 · Breiter · 2011 [cited by applicant]
US 8307368B2 · Wolf et al. · 2012 [cited by applicant]
US 8379656B2 · Waldrop et al. · 2013 [cited by applicant]
US 8407190B2 · Prahlad et al. · 2013 [cited by applicant]
US 8468033B2 · Gunn · 2013 [cited by applicant]
US 8509249B2 · Waldrop et al. · 2013 [cited by applicant]
US 8537845B2 · Waldrop et al. · 2013 [cited by applicant]
US 8583503B2 · Waldrop et al. · 2013 [cited by applicant]
US 8751323B2 · Waldrop et al. · 2014 [cited by applicant]
US 8752017B2 · Hossain · 2014 [cited by examiner]
US 8768652B1 · Mirtich et al. · 2014 [cited by applicant]
US 8825861B2 · Rao · 2014 [cited by applicant]
US 8891439B2 · Casey · 2014 [cited by applicant]
US 8892708B2 · Merrill et al. · 2014 [cited by applicant]
US 8918860B1 · Enderwick · 2014 [cited by examiner]
US 9009858B2 · Sapp et al. · 2015 [cited by applicant]
US 9110976B2 · Bolgert et al. · 2015 [cited by applicant]
US 9137209B1 · Brandwine et al. · 2015 [cited by applicant]
US 9203784B2 · Chang et al. · 2015 [cited by applicant]
US 9239740B2 · Zhao et al. · 2016 [cited by applicant]
US 9246840B2 · Anderson et al. · 2016 [cited by applicant]
US 9269061B2 · Jeyapaul et al. · 2016 [cited by applicant]
US 9300633B2 · Acharya et al. · 2016 [cited by applicant]
US 9338214B2 · Hinks · 2016 [cited by applicant]
US 9367362B2 · Kern · 2016 [cited by applicant]
US 9507622B2 · Robinson · 2016 [cited by examiner]
US 9525564B2 · Lee · 2016 [cited by applicant]
US 9531814B2 · Cardona-Gonzalez et al. · 2016 [cited by applicant]
US 9606819B2 · Wang et al. · 2017 [cited by applicant]
US 9667470B2 · Prathipati · 2017 [cited by examiner]
US 9736556B2 · Lingampalli · 2017 [cited by applicant]
US 9875086B1 · Anderson et al. · 2018 [cited by applicant]
US 9886267B2 · Maheshwari et al. · 2018 [cited by applicant]
US 9887876B2 · Kumar et al. · 2018 [cited by applicant]
US 9900219B2 · Huey et al. · 2018 [cited by applicant]
US 9948552B2 · Teng et al. · 2018 [cited by applicant]
US 9983860B1 · Koty et al. · 2018 [cited by applicant]
US 10116499B2 · Kumar et al. · 2018 [cited by applicant]
US 10129078B2 · Kumar et al. · 2018 [cited by applicant]
US 10230571B2 · Rangasmy et al. · 2019 [cited by applicant]
US 10382266B1 · Balakrishnan et al. · 2019 [cited by applicant]
US 10437575B2 · Chen · 2019 [cited by applicant]
US 10594801B2 · Cardona-Gonzalez et al. · 2020 [cited by applicant]
US 10764126B2 · Kumar et al. · 2020 [cited by applicant]
US 11218363B2 · Kumar et al. · 2022 [cited by applicant]
US 11936518B2 · Kumar et al. · 2024 [cited by applicant]
US 20040205101A1 · Radhakrishnan · 2004 [cited by applicant]
US 20050036483A1 · Tomisaka et al. · 2005 [cited by applicant]
US 20060041641A1 · Breiter et al. · 2006 [cited by applicant]
US 20060069777A1 · Kato et al. · 2006 [cited by applicant]
US 20080016518A1 · Yokoyama et al. · 2008 [cited by applicant]
US 20080043760A1 · Venkatraman · 2008 [cited by examiner]
US 20080261191A1 · Woolf et al. · 2008 [cited by applicant]
US 20090164973A1 · Barnett et al. · 2009 [cited by applicant]
US 20100299437A1 · Moore · 2010 [cited by applicant]
US 20100332454A1 · Prahlad et al. · 2010 [cited by applicant]
US 20110058547A1 · Waldrop et al. · 2011 [cited by applicant]
US 20110119088A1 · Gunn · 2011 [cited by applicant]
US 20110246627A1 · Kern · 2011 [cited by applicant]
US 20110246992A1 · Kern · 2011 [cited by applicant]
US 20120096525A1 · Bolgert et al. · 2012 [cited by applicant]
US 20120151063A1 · Yang et al. · 2012 [cited by applicant]
US 20120180071A1 · Lesandro et al. · 2012 [cited by applicant]
US 20120331149A1 · Rao · 2012 [cited by applicant]
US 20130013442A1 · Waldrop et al. · 2013 [cited by applicant]
US 20130019015A1 · Devarakonda et al. · 2013 [cited by applicant]
US 20130136138A1 · Miller et al. · 2013 [cited by applicant]
US 20130159256A1 · Fischer · 2013 [cited by examiner]
US 20130166504A1 · Varkhedi · 2013 [cited by examiner]
US 20130263209A1 · Panuganty · 2013 [cited by examiner]
US 20130283364A1 · Chang et al. · 2013 [cited by applicant]
US 20130325928A1 · Milburn et al. · 2013 [cited by applicant]
US 20130346569A1 · Smith et al. · 2013 [cited by applicant]
US 20140123135A1 · Huang · 2014 [cited by examiner]
US 20140164624A1 · Ames · 2014 [cited by examiner]
US 20140173594A1 · Ng et al. · 2014 [cited by applicant]
US 20140189692A1 · Wang et al. · 2014 [cited by applicant]
US 20140196028A1 · Macpherson · 2014 [cited by examiner]
US 20140244851A1 · Lee · 2014 [cited by applicant]
US 20140289791A1 · Acharya et al. · 2014 [cited by applicant]
US 20140324911A1 · De Lavarene et al. · 2014 [cited by applicant]
US 20140365662A1 · Dave · 2014 [cited by examiner]
US 20150121155A1 · Boshev · 2015 [cited by examiner]
US 20150135160A1 · Gauvin et al. · 2015 [cited by applicant]
US 20150161681A1 · Maes et al. · 2015 [cited by applicant]
US 20150229645A1 · Keith et al. · 2015 [cited by applicant]
US 20150249701A1 · Anand et al. · 2015 [cited by applicant]
US 20150288621A1 · Field · 2015 [cited by examiner]
US 20150324215A1 · Borthakur · 2015 [cited by examiner]
US 20160021197A1 · Pogrebinsky et al. · 2016 [cited by applicant]
US 20160112475A1 · Lawson et al. · 2016 [cited by applicant]
US 20160124742A1 · Rangasamy et al. · 2016 [cited by applicant]
US 20160127199A1 · Ding et al. · 2016 [cited by applicant]
US 20160127254A1 · Kumar et al. · 2016 [cited by applicant]
US 20160127454A1 · Maheshwari et al. · 2016 [cited by applicant]
US 20160308762A1 · Teng · 2016 [cited by examiner]
US 20160337175A1 · Rao · 2016 [cited by applicant]
US 20160344590A1 · Huey et al. · 2016 [cited by applicant]
US 20170155686A1 · Yanacek et al. · 2017 [cited by applicant]
US 20170187785A1 · Johnson et al. · 2017 [cited by applicant]
US 20170244593A1 · Rangasamy et al. · 2017 [cited by applicant]
US 20180262391A1 · Jung et al. · 2018 [cited by applicant]
US 20200120166A1 · Cardona-Gonzalez et al. · 2020 [cited by applicant]
US 20220131744A1 · Kumar et al. · 2022 [cited by applicant]
US 20240223443A1 · Kumar et al. · 2024 [cited by applicant]
US 20240372913A1 · Prasannakumar · 2024 [cited by examiner]
CN 102246474A · 2011 [cited by applicant]
CN 103209200A · 2013 [cited by applicant]
CN 103650456A · 2014 [cited by applicant]
JP 2008022264A · 2008 [cited by applicant]
JP 2012511293A · 2012 [cited by applicant]
JP 2013504269A · 2013 [cited by applicant]
JP 2013504270A · 2013 [cited by applicant]
WO 2012075448A1 · 2012 [cited by applicant]
“8.1.5.3 Generating a REST Controller Using Scaffolding,” Grails, retrieved from htlp://grails.github.io/grails-doc/2.3.7/ uide/webServices.html#generatingRestControllers/, Sep. 7, 2015, 18 pp. [cited by applicant]
“Bumm,” retrieved from https://www.npmjs.com/package/bumm, Sep. 2, 2015, 4 pp. [cited by applicant]
“Developing Front-End Microservices With Polymer Web Components and Test-Driven Development (Part 5-5) Using Microservices Technology Conversations,” retrieved from https://technologyconversations.com/2015/08/09/develop… [cited by applicant]
“Equinix Launches Cloud Exchange to Unlock Full Potential of Cloud Computing,” Equinix, Apr. 30, 2014, 5 pp. [cited by applicant]
“Rack-Scaffold-Master,” GitHub—mattt/rack-scaffold: Automatically generate RESTful CRUD services, retrieved from https://github.com/mattt/rack-scaffold, Aug. 28, 2014, 2 pp. [cited by applicant]
“Rest—How to Use Scaffolding and RESTfulness Together in Grails 2.3—Stack Overflow,” retrieved from http://stackoverflow.com/questions/19465421/how-to-use-scaffolding-and-restfulness-together in Grails 2.3, Oct. 19, 201… [cited by applicant]
“Step 3 Use a Generator to Scaffold Out your App,” Yeoman, retrieved from http://yeoman.io/codelab/scaffold-app.html, Sep. 2, 2015, 6 pp. [cited by applicant]
Abrams et al., “An Emergent Micro-Services Approach to Digital Curation Infrastructure,” The International Journal of Digital Curation, vol. 5, No. 1, Jun. 22, 2010, 15 pp. [cited by applicant]
Banikazemi et al., “Meridian: an SON platform for cloud network services”, IEEE Communications Magazine, IEEE Service Center, vol. 51, No. 2, Piscataway, US, Feb. 1, 2013, pp. 120-127. [cited by applicant]
Cortis, “REST and Scaffolding,” retrieved from http://www.slideshare.net/kcortis/rails-girlsgalwayestscaffoldingkeith, Jul. 5, 2014, 7 pp. [cited by applicant]
Dillon, “How to Write a Ruby and Rails 3 REST API,” Squarism, retrieved from squarism.com/2011/04/01/how-to-write-a-ruby-rails-3-rest-api/, Apr. 1, 2011, 19 pp. [cited by applicant]
Equinix HD “Episode 6: How to join the Equinix Cloud Exchange,” Equinix Videos, YouTube, Jul. 14, 2014, 1 pp. Retrieved from the Internet: https://www.youtube.com/watch?v=_FnnTRssh4o. [cited by applicant]
Equinixvideos: “Equinix HD 1 Episode 1: Performance Hub w/ Anirvan Das”, YouTube, Mar. 19, 2014 (Mar. 19, 2014), p. 1 pp., XP054980316, Retrieved from the Internet: URL:https://www.youtube.com/watch?v=110aDEv6M7k [retri… [cited by applicant]
Equinixvideos: “Equinix HD 1 Episode 4: Equinix Cloud Exchange w/ Bill Long”, youtube, Apr. 30, 2014 (Apr. 30, 2014), p. 1 pp., XP054978199, Retrieved from the Internet: URL:https://www.youtube.com/watch?v=iDSuvOiL8LA [… [cited by applicant]
Examination Report from counterpart Australian Application No. 2015338902, dated Nov. 1, 2017, 2 pp. [cited by applicant]
Examination Report from counterpart Australian Application No. 2019200821, dated Nov. 21, 2019, 2 pp. [cited by applicant]
Examination Report from counterpart European Application No. 15794014.9, dated Apr. 15, 2018, 7 pp. [cited by applicant]
Examination Report from counterpart European Application No. 19205162.1, dated Apr. 6, 2021, 10 pp. [cited by applicant]
Examination Report No. 1 from counterpart Australian Application No. 2022201786 dated Mar. 14, 2023, 3 pp. [cited by applicant]
Extended European Search Report of European Application No. 19205162.1 mailed Apr. 7, 2020, 14 pp. [cited by applicant]
First Examination Report from counterpart Australian Patent Application No. 2020203877, dated Mar. 16, 2021, 4 pp. [cited by applicant]
First Office Action and Search Report, and translation thereof, from counterpart Chinese Application No. 2015800323212, dated Dec. 25, 2018, 11 pp. [cited by applicant]
Genuitec, “Scaffolding a Spring MVC Application,” retrieved from https://www.genuitec.com/products/myeclipse/learning-center/spring/spring-3-0-mvc-scaffolding/, Sep. 2, 2015, 16 pp. [cited by applicant]
International Preliminary Report on Patentability from International Application No. PCT/US2015/058500, mailed Feb. 8, 2017, 7 pp. [cited by applicant]
International Search Report and Written Opinion from International Application number PCT/US2015/058500, dated Feb. 11, 2016, 20 pp. [cited by applicant]
Invitation to Respond to Written Opinion from Singaporean Application No. 10202004184R, dated Jul. 5, 2022, 8 pp. [cited by applicant]
Jazayeri et al., “Some Trends in Web Application Development,” Future of Software Engineering (FOSE '07), Jun. 2007, 14 pp. [cited by applicant]
Kovacevic, “RESTful Admin Namespaced Controller Using Scaffolding,” retrieved from http://icebergist.com/posts/ restful-admin-namespaced-controller-using-scaffolding/, Sep. 17, 2008, 4 pp. [cited by applicant]
Namiot et al., “On Micro-services Architecture,” International Journal of Open Information Technologies ISSN: 2307-8162 vol. 2, No. 9, Aug. 20, 2014, 4 pp. [cited by applicant]
Notice of Acceptance dated Jun. 18, 2018, from counterpart Australian Application No. 2015338902, 3 pp. [cited by applicant]
Notice of Acceptance from counterpart Australian Patent Application No. 2018236712, dated Oct. 25, 2018, 3 pp. [cited by applicant]
Notice of Allowance from counterpart Canadian Application No. 3,146,289, dated Jun. 28, 2022, 1 pp. [cited by applicant]
Notice of Intent to Grant from counterpart Application No. 11 2016 029210-3 dated Mar. 7, 2023, 1 pp. [cited by applicant]
Notice of Intent to Grant from counterpart Canadian Application No. 2,951,939 dated Oct. 12, 2022, 1 pp. [cited by applicant]
Notice of Intent to Grant from counterpart Singaporean Application No. 10202004184R dated Sep. 20, 2024, 4 pp. [cited by applicant]
Office Action from counterpart Canadian Application No. 2,951,939 dated Oct. 23, 2017, 4 pp. [cited by applicant]
Office Action from counterpart Canadian Application No. 2,951,939 dated Sep. 10, 2021, 4 pp. [cited by applicant]
Office Action from counterpart Canadian Application No. 2,951,939, dated Oct. 3, 2018, 6 pp. [cited by applicant]
Office Action from counterpart Canadian Application No. 2,951,939, dated Sep. 30, 2019, 3 pp. [cited by applicant]
Okawara, “Equinix, linking multiple cloud services Cloud Exchange,” Equinix, Jun. 4, 2014, 3 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 14/927,306, dated Sep. 6, 2017 through Aug. 30, 2018, 91 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 14/927,315, dated Mar. 14, 2018 through Oct. 24, 2018, 44 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 14/927,451, dated Jun. 22, 2017 through Nov. 1, 2017, 31 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 15/395,101, dated Jan. 27, 2017 through Oct. 23, 2017, 57 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 15/887,165, dated Apr. 13, 2018 through Jul. 23, 2018, 33 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 16/172,501, dated Feb. 26, 2019 through May 15, 2020, 40 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 17/007,929, dated Aug. 17, 2021 through Dec. 1, 2021, 12 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 17/646,375, dated Sep. 23, 2022 through Mar. 30, 2023, 7 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 18/146,331, dated Jun. 15, 2023 through Nov. 14, 2023, 42 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 18/607,373, dated Jul. 24, 2024 through Dec. 5, 2024, 24 pp. [cited by applicant]
Reply to Written Opinion dated Feb. 11, 2016, filed Aug. 30, 2016 from counterpart International Application No. PCT/US2015/058500, 21 pgs. [cited by applicant]
Response to Canadian Office Action dated Oct. 23, 2017, from counterpart Canadian application number 2,951,939, filed Apr. 20, 2018, 19 pp. [cited by applicant]
Response to Communication pursuant to Rules 70(2) and 70a(2) dated May 27, 2020, from counterpart European Application No. 19205162.1, filed Nov. 20, 2020, 204 pp. [cited by applicant]
Response to Examination Report dated Apr. 6, 2021, from counterpart European Application No. 19205162.1, filed Oct. 15, 2021, 8 pp. [cited by applicant]
Response to Examination Report dated Oct. 5, 2018, from counterpart European Application No. 15794014.9, filed Oct. 5, 2018, 20 pp. [cited by applicant]
Response to Notification of Reasons for Rejection dated Apr. 24, 2018, from counterpart Japanese application number 2016-573992, filed Nov. 26, 2018, 17 pp. [cited by applicant]
Response to Office Action dated Sep. 10, 2021, from counterpart Canadian Application No. 2,951,939 filed Jan. 20, 2022, 12 pp. [cited by applicant]
Response to Office Action filed in Canadian Application No. 2,951,939 on Mar. 13, 2020, 10 pp. [cited by applicant]
Response to Written Opinion dated Jul. 5, 2022, from counterpart Singaporean Application No. 10202004184R filed Nov. 29, 2022, 19 pp. [cited by applicant]
Rosen et al., “BGP/MPLS IP Virtual Private Networks (VPNs),” RFC 4364, Feb. 2006, Internet Engineering Task Force(IETF) Network Working Group, 47 pp. [cited by applicant]
Ruby et al., “Agile Web Development with Rails 5.1,” The Pragmatic Bookshelf, Nov. 2017, 10 pp. [cited by applicant]
Scofield, “Rails 3 Generators Scaffolding,” retrieved from https://www.viget.com/articles/rails-3-generatorscaffolding, Mar. 2, 2010, 3 pp. [cited by applicant]
Second Written Opinion of International Application No. PCT/US2015/058500, mailed Oct. 10, 2016, 6 pp. [cited by applicant]
Stafford, “Building a Microservices-based REST API with RestExpress, Java EE, and MongoDB Part 2, Programmatic Ponderings,” retrieved from htlp://programmaticponderings.worldpress.com/2015/05/31/building-amicroservices-… [cited by applicant]
Summons to Attend Oral Proceedings Issued in EP Application No. 15794014.9 mailed May 21, 2019, 11 pp. [cited by applicant]
Summons to Attend Oral Proceedings Pursuant to Rule 115(1) EPC from counterpart European Application No. 19205162.1 dated May 27, 2022, 13 pp. [cited by applicant]
The Notification of Reason for Rejection, and translation thereof, from counterpart Japanese Application No. 2016-573992, mailed Apr. 24, 2018, 9 pp. [cited by applicant]
Thomas, “REST, Scaffolding, and Data Models Ruby on Rails,” retrieved from http://jacobjthomas.com/rubyonrails/rest_scaffolding_user_micropost_data_model/, Aug. 22, 2013, 8 pp. [cited by applicant]
Wintermeyer, “5.2. Generating a Scaffold,” retrieved from http://www.xyzpub.com/en/ruby-on-rails/3.21 scaffold_anlegen.html, Sep. 2, 2015, 18 pp. [cited by applicant]