Hub-and-spoke connection architecture

Patent metadata

Field	Value
Publication number	US-10084886-B2
Application number	US-201715587826-A
Country	US
Kind code	B2
Filing date	May 5, 2017
Priority date	Dec 30, 2015
Publication date	Sep 25, 2018
Grant date	Sep 25, 2018

Abstract

A system, may include a private cloud network operated by an operator for a client. The private cloud network may be connected to a public cloud network that operates a web platform and a plurality of groups of gateway devices. A first group of gateway devices may be located at an operator data center associated with the operator, and may provide connectivity for the operator data center to connect to the public cloud network via the private cloud network. A second group of gateway devices may be located at a client data center associated with the client, and may provide connectivity for the client data center to connect to the public cloud network via the private cloud network. The private cloud network may be connected to the public cloud network, the operator data center, and the client data center in a hub-and-spoke connection configuration.

First claim

What is claimed is:

1. A method, comprising:
receiving, by a device, configuration information associated with configuring routing for a system,
the system including a public cloud network, a private cloud network, an operator data center, a franchisor data center, and one or more franchisee data centers,
the public cloud network being associated with operating a web platform for receiving a product order relating to a take-out or delivery of a food product,
the system being configured in a hub-and-spoke connection configuration;

selectively propagating, by the device, the configuration information associated with configuring routing for the system,
the configuration information including one or more routes for routing information from/to the public cloud network;

receiving, by the device, payload data for routing from a first spoke of the hub-and-spoke connection configuration to a second spoke of the hub-and-spoke connection configuration, after selectively propagating the configuration information; and
selectively routing, by the device, the payload data to the second spoke of the hub-and-spoke connection configuration.

2. The method of claim 1 , where receiving the configuration information, comprises:
receiving the configuration information from a device of the operator data center,
the operator data center being authorized to configure routing for the system; and

where selectively propagating the configuration information comprises:
propagating the configuration information to a gateway device of the public cloud network, the private cloud network, the franchisor data center, or the one or more franchisee data centers to cause a gateway device to propagate a route for routing payload data based on receiving the configuration information from the gateway device of the operator data center.

3. The method of claim 1 , where receiving the configuration information, comprises:
receiving a trigger to transmit a border gateway protocol (BGP) message advertising a route for payload data; and
where selectively propagating the configuration information comprises:
transmitting the BGP message.

4. The method of claim 1 , where a franchisee data center is added to the system; and
where receiving the configuration information comprises:
receiving configuration information associated with identifying one or more routes for routing network traffic between the franchisee data center and the public cloud network; and

where selectively propagating the configuration information comprises:
propagating the configuration information to at least one of:
a gateway device of the franchisee data center, or
a gateway device of the private cloud network.

5. The method of claim 1 , where the configuration information is included in a border gateway protocol (BGP) extended community message.

6. The method of claim 1 , where selectively routing the payload data to the second spoke comprises:
failing to route the payload data when neither the first spoke nor the second spoke is the public cloud network.

7. The method of claim 1 , further comprising:
providing, based on receiving the payload data, information identifying a network traffic usage associated with the first spoke or the second spoke,
the information identifying the network traffic usage being associated with at least one of:
network traffic usage based network resource allocation, or
network traffic usage based billing.

8. A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors, cause the one or more processors to:
receive configuration information associated with configuring routing for a system,
the system including a public cloud network providing an ecommerce web platform, a private cloud network providing routing of information, an operator data center providing operation services, and a plurality of client data centers connected to a plurality of store locations associated with the ecommerce web platform,
the system being configured in a hub-and-spoke connection configuration,
the configuration information including information identifying one or more routes for directing network traffic of the system;

selectively propagate the configuration information associated with configuring routing for the system to cause payload data to be directed via the one or more routes for directing network traffic of the system;
receive payload data for routing after selectively propagating the configuration information; and
selectively route the payload data based on the configuration information.

9. The computer-readable medium of claim 8 , where the operator data center is connected to the private cloud network via a first link associated with a first telecommunications provider, the plurality of client data centers are connected via a plurality of second links associated with a second telecommunications provider, and a third link is an Azure ExpressRoutes connection,
the first telecommunications provider being different from the second telecommunications provider.

10. The computer-readable medium of claim 8 , where the configuration information is included in a border gateway protocol (BGP) extended community message.

11. The computer-readable medium of claim 8 , where the payload data includes order information associated with a particular store location of the plurality of store locations; and
where the one or more instructions, that cause the one or more processors to selectively route the payload data, further cause the one or more processors to:
route the payload data to one of the plurality of client data centers to cause the one of the plurality of client data centers to route the payload data to the particular store location.

12. The computer-readable medium of claim 8 , where the cloud based web platform includes a group of Hybris data hub servers associated with receiving orders and transmitting the orders as payload data.

13. The computer-readable medium of claim 8 , where the one or more instructions, that cause the one or more processors to receive the configuration information, cause the one or more processors to:
receive a message including the configuration information; and
where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
determine that the message is transmitted from a gateway device; and
determine that the message is not to be propagated based on the gateway device being associated with one of the plurality of client data centers.

14. A device, comprising:
one or more processors to:
receive configuration information associated with configuring routing for a system,
the system including a public cloud network, a private cloud network, an operator data center, a franchisor data center, and one or more franchisee data centers,
public cloud network being associated with operating a web platform for receiving a product order relating to a take-out or delivery of a food product, and
the system being configured in a hub-and-spoke connection configuration;

selectively propagate the configuration information associated with configuring routing for the system,
the configuration information including one or more routes for routing information from/to the public cloud network;

receive payload data for routing from a first spoke of the hub-and-spoke connection configuration to a second spoke of the hub-and-spoke connection configuration, after selectively propagating the configuration information; and
selectively route the payload data

Assignees

• Accenture Global Solutions Ltd

Inventors

• Ryan Jeffrey Stanford
• Stevenson John
• Nahhas Bahij

Classifications

• H04L43/0876

  Network utilisation, e.g. volume of load or congestion level · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• G06Q30/0635

  replenishment orders; recurring orders · CPC title

• H04L67/34 Primary

  involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title

• G06Q50/12

  Hotels or restaurants · CPC title