Network component placement architecture

Patent metadata

Field	Value
Publication number	US-11303539-B2
Application number	US-201514832458-A
Country	US
Kind code	B2
Filing date	Aug 21, 2015
Priority date	Dec 5, 2014
Publication date	Apr 12, 2022
Grant date	Apr 12, 2022

Abstract

A network component placement architecture addresses the difficult technical challenge of determining where specific technical components of an overall service may be provisioned. The architecture is particularly effective at determining where, among a myriad of possible service provides, platforms, and regions, the technical components can be placed and meet all of the applicable technical constraints on the placement of the technical components. In one implementation, the placement architecture includes a sequence of pipeline stages that define an analysis sequence leading to a set of possible placement options.

First claim

What is claimed is:

1. A system comprising:
a communication interface configured to receive a technical service request for a technical service from a resource requester; and
a processor in communication with the communication interface and a memory, wherein the memory stores instruction code that causes the processor to:
responsive to the technical service request, request resource requester metadata by providing a metadata completion template including a series of metadata queries configured to characterize the resource requester for application of a mapping rule configured to translate a designation of an expected number of users from the requester metadata into specific sets of virtual machine hardware technical specifications to handle an expected load associated with the expected number of users, the specific sets each specifying for the expected load:
a number of processor cores; and
a quantity of random access memory (RAM);

responsive to the metadata completion template, receive the resource requester metadata in a pre-defined structured data format;
determine the expected load associated with the expected number of users using the designation of the expected number of users;
using the expected load, determine the mapping rule;
based on the resource requester metadata, determine, using the mapping rule, feasible placement options for the technical service by filtering candidate placement options at a capacity stage of multiple sequential pipeline processing stages, wherein the candidate placement options correspond to instantiable computer network resources located in different geographic regions provided by different service providers;
impose an ordering upon the feasible placement options, the ordering defined using a metric specified within the resource requestor metadata;
present the feasible placement options, according to the ordering, to the resource requester through the communication interface; and
based on presentation of the feasible placement options, cause instantiation of computer network resources at a geographic region associated with a selected feasible placement option by translating the specific sets in to a virtual machine size selection among multiple virtual machine sizes available via the selected feasible placement option,
wherein the stored instruction code further causes the processor to:
determine to which service provider regions the resource requester has active subscription based on the resource requester metadata and service provider metadata;
for iteration:
determine whether a service provider region in the feasible placement options is available to the resource requester based on subscription information;
when it is determined that the service provider region in the feasible placement options is available to the resource requester based on the subscription information, determine whether an additional service provider region in the feasible placement options is needed for consideration; and
when it is determined that the service provider region in the feasible placement options is not available to the resource requester based on the subscription information, remove the service provider region from the feasible placement options and determine whether the additional service provider region in the feasible placement options is needed for consideration;

when it is determined that the additional service provider region in the feasible placement options is needed for consideration, repeat the iteration; and
when it is determined that the additional service provider region in the feasible placement options is not needed for consideration, exit the iteration and determine the feasible placement options responsive to the determined service provider regions.

2. The system of claim 1 , wherein the processor: receives a technical service template specifying a baseline technical component type for implementing the technical service;
determines which service provider regions support the baseline technical component type; and
determines the feasible placement options responsive to the service provider regions.

3. The system of claim 2 , wherein the processor:
initiates processing by type-to-type analysis circuitry on the baseline technical component type;
determines, in response to the processing, additional service provider regions that support an equivalent for the baseline technical component type; and
determines the feasible placement options responsive to the additional service provider regions.

4. The system of claim 1 , wherein the processor:
receives a technical service template specifying a baseline technical asset for implementing the technical service;
determines which service provider regions support the baseline technical asset; and
determines the feasible placement options responsive to the service provider regions.

5. The system of claim 4 , wherein the processor:
initiates processing by type-to-type analysis circuitry on the baseline technical asset;
receives, in response to the processing, additional service provider regions that support an equivalent for the baseline technical asset; and
determines the feasible placement options responsive to the additional service provider regions.

6. The system of claim 1 , wherein the processor:
receives a technical service template specifying a baseline network for connecting to the technical service;
determines which service provider regions connect to the baseline network; and
determines the feasible placement options responsive to the service provider regions.

7. The system of claim 6 , wherein the processor:
initiates processing by type-to-type analysis circuitry on the baseline network;
receives, in response to the processing, additional service provider regions that support an equivalent for the baseline network; and
determines the feasible placement options responsive to the additional service provider regions.

8. The system of claim 1 , wherein the processor:
receives a technical service template specifying an implementation of the technical service;
determines which service provider regions currently have capacity to accept provisioning of the implementation of the technical service; and
determines the feasible placement options responsive to the service provider regions.

9. The system of claim 1 , wherein the processor:
receives a technical service template specifying an implementation of the technical service;
determines which service provider regions qualify to provision the implementation of the technical service; and
determines the feasible placement options responsive to the service provider regions.

10. The system of claim 9 , wherein the processor:
determine, based on the requester metadata, particular requirements of the resource requester;
receive service provider metadata specifying capabilities of service providers; and
determines which service providers regions qualify responsive to the resource requester metadata and the service provider metadata.

11. A product comprising:
machine-readable media other than a transitory signal; and
instructions stored on the machine-readable media, the instructions configured to, when executed, cause a machine to:
receive, at a communication interface, a technical service request for a technical service from a resource requester; and
at placement pipeline circuitry in communication with the communication interface, the placement pipeline circuitry comprising multiple sequential pipeline processing stages:
responsive to the technical service request, request resource requester metadata by providing a metadata completion template including a series of metadata queries configured to char

Assignees

• Accenture Global Services Ltd

Inventors

• Cimprich Patrick Francis
• Deluca Michael Gerald
• Cantwell Jack Q W
• Peterson Sean David
• Wells Marshall J

Classifications

• H04L47/83

  based on usage prediction · CPC title

• H04L67/1001

  for accessing one among a plurality of replicated servers · CPC title

• H04L67/60

  Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70) · CPC title

• H04L67/565

  Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561) · CPC title

• H04L67/51

  Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title