Patent Description:
Typically, traffic routing in a cloud environment is defined by the cloud provider. The workload submitted to the cloud environment by tenants has to adhere to the underlying IP connectivity. However, with dynamic workloads in tenant environments, often the prescribed traffic routing for any particular workload may not be optimal. The traffic routing rules in place, for example, may not match very well the needs of the workload. The mis-match between routing rules defined by the service or cloud provider and the functionality of the actual workload reduces the efficiency of the cloud environment and can increase frustration on the part of the tenant and their cloud provider as well.

<CIT> describes a system and method for establishing one or more virtual backbone tunnels coupled with an existing network infrastructure and dedicated to a particular user for facilitating the transmission of soft bandwidth services across the network.

<CIT> describes a service provider management device that provides a plurality of redundant fabric motifs, and receives virtual data center tenant selection of one or more of the redundant fabric motifs for particular pairs of data center segments of the virtual data center.

The disclosure will be readily understood by the following detailed description in conjunction with the accompanying drawings in which:.

The invention to which the present European patent relates is defined in the appended claims.

It is a widely recognized (and often frustrating) fact that there is a lack of tenant-specific routing capabilities in cloud environments. As noted above, when the cloud environment management system imposes routing and pathway requirements on tenants and their workload, inefficiencies can result. There is an ever-increasing need to address these issues and to be able to define routing on a per-tenant or a per-workload basis. Each tenant needs to be able to define their routing environment based on application requirements. The concepts disclosed herein address the issues in the art and solve these problems in a simple, but novel, manner. In addition, tenant applications should be able to modify routing in real-time, on-demand, dynamically and in an automated fashion.

Disclosed is a system and method of providing a segment routing as a service application. Segment routing is used to abstract the routing from the IP addresses and use the concepts of segments to do route forwarding. The concepts disclosed herein involve using segments as the basis for making decisions about how to reach a destination in a network pathway. The segment routing as a service (SRaaS) disclosed herein is an application running on a cloud device that provides application programming interfaces (APIs) to achieve a more flexible and beneficial approach to managing routing using segments. By using SRaaS, the system can modify the segment routing environment depending on what the tenant needs for a particular workload.

Feedback is provided in real-time back to the service provider such that real-time, dynamic modifications and changes can be implemented in the routing rules. For example, a new workload can be introduced into a cloud environment by a tenant. The workload may have parameters that cause data from a database to be routed to a virtual machine for processing according to a first path and based on the tenant-defined layer <NUM> overlay segment routing rules. However, after the workload starts processing, the pathway may not provide as much bandwidth as is required by a service level agreement or perhaps a node has gone down along that path in the cloud environment. Feedback can be received which causes a modification of the tenant-defined layer <NUM> overlay segment routing rules which will cause the data for the workload to take a different path and thus fulfill SLA or other requirements. The solution herein enables a segment routing as a service application to perform not only such defined routing on a per-tenant basis, but also further enable real-time dynamic modifications to the defined routing according to feedback.

The present disclosure addresses the issues in the art and provides a solution using segment routing. Segment routing is defined in many different IETF drafts/RFCs (see an overview here: http://www. segment- routing. net/home/ietf). The present disclosure focuses on the implementation of segment routing in a new way "as a Service" (aaS) within a cloud environment such that it allows on-demand and per-tenant routing definitions and modifications.

Implementing segment routing as a service (SRaaS) enables an on-demand, dynamic and automated configuration of underlying segment routing environments by tenants, their applications and the service provider. The south-bound APIs provided by SRaaS allows RESTful API calls to the segment routing enabled infrastructure or alternatively a segment routing controller.

The disclosure first turns to <FIG> which discloses some basic hardware components that can apply to system examples of the present disclosure. Following the discussion of the basic example hardware components, the disclosure will turn to the segment routing as a service concept.

With reference to <FIG>, an exemplary system and/or computing device <NUM> includes a processing unit (CPU or processor) <NUM> and a system bus <NUM> that couples various system components including the system memory <NUM> such as read only memory (ROM) <NUM> and random access memory (RAM) <NUM> to the processor <NUM>. The system <NUM> can include a cache <NUM> of high-speed memory connected directly with, in close proximity to, or integrated as part of the processor <NUM>. The system <NUM> copies data from the memory <NUM>, <NUM>, and/or <NUM> and/or the storage device <NUM> to the cache <NUM> for quick access by the processor <NUM>. In this way, the cache provides a performance boost that avoids processor <NUM> delays while waiting for data. These and other modules can control or be configured to control the processor <NUM> to perform various operations or actions. Other system memory <NUM> may be available for use as well. The memory <NUM> can include multiple different types of memory with different performance characteristics. It can be appreciated that the disclosure may operate on a computing device <NUM> with more than one processor <NUM> or on a group or cluster of computing devices networked together to provide greater processing capability. The processor <NUM> can include any general purpose processor and a hardware module or software module, such as module <NUM><NUM>, module <NUM><NUM>, and module <NUM><NUM> stored in storage device <NUM>, configured to control the processor <NUM> as well as a special-purpose processor where software instructions are incorporated into the processor. The processor <NUM> may be a self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric. The processor <NUM> can include multiple processors, such as a system having multiple, physically separate processors in different sockets, or a system having multiple processor cores on a single physical chip. Similarly, the processor <NUM> can include multiple distributed processors located in multiple separate computing devices, but working together such as via a communications network. Multiple processors or processor cores can share resources such as memory <NUM> or the cache <NUM>, or can operate using independent resources. The processor <NUM> can include one or more of a state machine, an application specific integrated circuit (ASIC), or a programmable gate array (PGA) including a field PGA.

The system bus <NUM> may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. A basic input/output system (BIOS) stored in ROM <NUM> or the like, may provide the basic routine that helps to transfer information between elements within the computing device <NUM>, such as during start-up. The computing device <NUM> further includes storage devices <NUM> or computer-readable storage media such as a hard disk drive, a magnetic disk drive, an optical disk drive, tape drive, solid-state drive, RAM drive, removable storage devices, a redundant array of inexpensive disks (RAID), hybrid storage device, or the like. The storage device <NUM> is connected to the system bus <NUM> by a drive interface. The drives and the associated computer-readable storage devices provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for the computing device <NUM>. In one aspect, a hardware module that performs a particular function includes the software component stored in a tangible computer-readable storage device in connection with the necessary hardware components, such as the processor <NUM>, bus <NUM>, an output device such as a display <NUM>, and so forth, to carry out a particular function. In another aspect, the system can use a processor and computer-readable storage device to store instructions which, when executed by the processor, cause the processor to perform operations, a method or other specific actions. The basic components and appropriate variations can be modified depending on the type of device, such as whether the computing device <NUM> is a small, handheld computing device, a desktop computer, or a computer server. When the processor <NUM> executes instructions to perform "operations", the processor <NUM> can perform the operations directly and/or facilitate, direct, or cooperate with another device or component to perform the operations.

Although the exemplary embodiment(s) described herein employs a storage device such as a hard disk <NUM>, other types of computer-readable storage devices which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, digital versatile disks (DVDs), cartridges, random access memories (RAMs) <NUM>, read only memory (ROM) <NUM>, a cable containing a bit stream and the like, may also be used in the exemplary operating environment. According to this disclosure, tangible computer-readable storage media, computer-readable storage devices, computer-readable storage media, and computer-readable memory devices, expressly exclude media such as transitory waves, energy, carrier signals, electromagnetic waves, and signals per se.

To enable user interaction with the computing device <NUM>, an input device <NUM> represents any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech and so forth. An output device <NUM> can also be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems enable a user to provide multiple types of input to communicate with the computing device <NUM>. The communications interface <NUM> generally governs and manages the user input and system output. There is no restriction on operating on any particular hardware arrangement and therefore the basic hardware depicted may easily be substituted for improved hardware or firmware arrangements as they are developed.

For clarity of explanation, the illustrative system embodiment is presented as including individual functional blocks including functional blocks labeled as a "processor" or processor <NUM>. The functions these blocks represent may be provided through the use of either shared or dedicated hardware, including, but not limited to, hardware capable of executing software and hardware, such as a processor <NUM>, that is purpose-built to operate as an equivalent to software executing on a general purpose processor. For example the functions of one or more processors presented in <FIG> can be provided by a single shared processor or multiple processors. (Use of the term "processor" should not be construed to refer exclusively to hardware capable of executing software. ) Illustrative embodiments may include microprocessor and/or digital signal processor (DSP) hardware, read-only memory (ROM) <NUM> for storing software performing the operations described below, and random access memory (RAM) <NUM> for storing results. Very large scale integration (VLSI) hardware embodiments, as well as custom VLSI circuitry in combination with a general purpose DSP circuit, may also be provided.

The logical operations of the various embodiments are implemented as: (<NUM>) a sequence of computer implemented steps, operations, or procedures running on a programmable circuit within a general use computer, (<NUM>) a sequence of computer implemented steps, operations, or procedures running on a specific-use programmable circuit; and/or (<NUM>) interconnected machine modules or program engines within the programmable circuits. The system <NUM> shown in <FIG> can practice all or part of the recited methods, can be a part of the recited systems, and/or can operate according to instructions in the recited tangible computer-readable storage devices. Such logical operations can be implemented as modules configured to control the processor <NUM> to perform particular functions according to the programming of the module. For example, <FIG> illustrates three modules Mod1 <NUM>, Mod2 <NUM> and Mod3 <NUM> which are modules configured to control the processor <NUM>. These modules may be stored on the storage device <NUM> and loaded into RAM <NUM> or memory <NUM> at runtime or may be stored in other computer-readable memory locations.

One or more parts of the example computing device <NUM>, up to and including the entire computing device <NUM>, can be virtualized. For example, a virtual processor can be a software object that executes according to a particular instruction set, even when a physical processor of the same type as the virtual processor is unavailable. A virtualization layer or a virtual "host" can enable virtualized components of one or more different computing devices or device types by translating virtualized operations to actual operations. Ultimately however, virtualized hardware of every type is implemented or executed by some underlying physical hardware. Thus, a virtualization compute layer can operate on top of a physical compute layer. The virtualization compute layer can include one or more of a virtual machine, an overlay network, a hypervisor, virtual switching, and any other virtualization application.

The processor <NUM> can include all types of processors disclosed herein, including a virtual processor. However, when referring to a virtual processor, the processor <NUM> includes the software components associated with executing the virtual processor in a virtualization layer and underlying hardware necessary to execute the virtualization layer. The system <NUM> can include a physical or virtual processor <NUM> that receive instructions stored in a computer-readable storage device, which cause the processor <NUM> to perform certain operations. When referring to a virtual processor <NUM>, the system also includes the underlying physical hardware executing the virtual processor <NUM>.

The disclosure now turns to <FIG> and <FIG> which illustrate segment routing as a service. <FIG> discloses an internet protocol environment <NUM>, a "segment routing as a service" (SRaaS) provider <NUM> and a representation <NUM> of the tenant-defined layer <NUM> overlay representing the internet protocol environment <NUM>. The tenant-defined layer <NUM> overlay segment routing rules can be associated with a layer <NUM> overlay defining a second configuration <NUM> of the internet protocol environment <NUM> between the first virtual machine and the second virtual machine, or between any two nodes. The two nodes can be of different types (processor, storage, database, memory, etc.) and one can be in a cloud environment and the other may be in a separate environment.

The internet protocol environment can include various elements <NUM>, <NUM>, <NUM> which can be such entities as switches, nodes, services, and so forth, that connect a first node such as a first virtual machine <NUM> with a second node such as a second virtual machine <NUM>. The internet protocol environment <NUM> communicates data (such as layer <NUM> environment data) to the SRaaS component <NUM>. Segment routing provides the means (using the source routing paradigms) to steer traffic through a list of segments. A segment can be defined as any type of instruction including topological and/or service functions (SF). The use of the segment allows the enforcement of routes through any topological path within a network deployment. The concepts disclosed herein leverage the capabilities of segment routing and extend segment routing (both systems and method) such that cloud tenants are able to specify the topological paths dynamically and on-demand.

Normally, segment routing may be simply implemented in a compute environment by a service provider and tenants would have to have their workload managed according to the segment routing rules defined for them. However, <FIG> shows segment routing as a service concepts which provide the additional feature of the tenant being able to specify layer <NUM> connectivity for a workload. The layer <NUM> connectivity can include the connectivity between different workloads based on application needs. The connectivity can also be between a processing node and a storage node, or between any two disparate types of nodes or services. The segment routing as a service component <NUM> will receive both the data from the environment <NUM> and the tenant-defined data and process both sets of data to output a tenant-defined layer <NUM> overlay <NUM> for the environment <NUM>. The overlay <NUM> shown by way of example in <FIG> illustrates the first virtual machine <NUM> communicating with the second virtual machine <NUM> with various nodes <NUM>, <NUM>, <NUM>, <NUM> there between.

As noted above, the first virtual machine <NUM> and the second virtual machine <NUM> can also represent any to different types of nodes or entities within the environment. For example, the second virtual machine <NUM> may represent a database that provides data to be communicated to the first virtual machine <NUM> for processing or carrying out the workload running on the first virtual machine <NUM>. The overlay environment can also provide feedback to the segment routing as a service component <NUM> to enable dynamic, real-time modifications to routing pathway rules. Receiving feedback associated with an application of the tenant-defined layer <NUM> overlay segment routing rules can result in the generation of an updated version of the tenant-defined layer <NUM> overlay segment routing rules. The feedback can include data on bandwidth and/or throughput, jitter, latency, QoS, performance, resource consumption, uptime or responsiveness, errors, cost, packet loss, packet duplication, availability, SLA related metrics, connectivity, error rate, response time, pricing requirements, changes or rates of change on one or more of these factors within the environment and/or specifically related to the workload, etc..

In one example, assume that an application running on a virtual machine <NUM> needs a large amount of data from a database. In this case, a larger amount of bandwidth is needed to transport from a hardware storage endpoint. Assume in this example, that node <NUM> is a storage device holding a large amount of data. The database <NUM> could also be separate from the cloud and be part of an enterprise environment. A company might want to store its proprietary data but utilize the cloud environment for computing power. The tenant in this case may want to ensure through the data it provides to the SRaaS <NUM> that the routing between its database <NUM> and the application running in the cloud <NUM> is defined in a certain way. This information can be part of what is specified by the tenant to the SRaaS <NUM>.

There are multiple aspects of the SRaaS that are contemplated, as well as various elements and benefits of the disclosure. First, SRaaS can be a way to overlay segment routing functionality <NUM> over any IP infrastructure <NUM>. The concepts enable dynamic and real-time modification of the forwarding path based on application needs. The concepts disclosed herein can also maintain segment routing path definitions on a per-virtual environment basis (i.e., virtual DC - i.e., an OpenStack project).

Implementing SRaaS <NUM> allows tenants to define forward paths per service or application, while being able to modify these based on application needs and real-time telemetry information. Tenants can leverage the APIs defined further below as a way to modify the segment routing overlay incorporating characteristics such as bandwidth, jitter, latency, pricing requirements, and/or any other metrics or factors as previously noted. These characteristics can be defined by tenant applications in advance or in real-time during run-time. In other words, the feedback that is represented in <FIG> can include real-time or near real-time information about bandwidth usage, jitter characteristics, changes in latency, pricing requirements (now the workload is operating during a peak usage time period and the price has gone up), error rate, packet loss, cost, connectivity, response time, performance, resource utilization, packet duplication, and so forth. In addition to tenants modifying the segment routing forwarding, applications can automatically adjust the forwarding based on dynamic and on-demand requirements (telemetry based information such as utilization of network links, application peak times, etc.). The data provided through feedback can also include rates of change, such as how much bandwidth is being restricted per minute or per every five minutes, which can enable the SRaaS <NUM> to select a time in which to dynamically modify the overlay and adjust the segment routing of the environment <NUM>.

An underlying IP environment <NUM> can be pre-configured using some Interior Gateway Protocol (IGP) protocol, such as OSPF, RIP, IS-IS, IGRP, etc. For example, Open Shortest Path First (OSPF) can be used, which is a routing protocol for Internet Protocol (IP) networks. It uses a link state routing algorithm and falls into the group of interior routing protocols, operating within a single autonomous system (AS). Segment routing <NUM> is then used as an overlay through the SRaaS application to define a "virtual routing topology" <NUM> on top of the underlying IP infrastructure <NUM>. Note that the SRaaS application can be a module within a Software-Defined Network (SDN) environment (i.e., OpenDaylight controller, VTS, etc.).

L3 infrastructure information can be fed into the SRaaS application <NUM> for defining the abstracted overlay segment routing logic. Here, the L3 infrastructure information is predominantly based on the IGP details (Routing Information Base (RIB) details, link costs, other IGP metrics (depending on underlying IGP), router capabilities, shortest path to other points in infrastructure (such as network functions, i.e. firewalls), etc.) defined in the infrastructure. SRaaS <NUM> can make this information available for providers, tenants and applications to aid in defining the segment routing overlay forwarding based on policies and thresholds. For example, the rules may provide guidance to avoid link X in the infrastructure if cost is higher than Y. The details provided herein can use the capabilities offered by the underlying IGP protocol, such as the Enhanced Interior Gateway Routing Protocol (EIGRP) or OSPF, and may use additional means to gather further environmental details that can influence the segment routing overlay (such as resource utilization, link utilization, etc.). The EIGRP is an advanced distance-vector routing protocol that is used on a computer network for automating routing decisions and configuration. The inventors envision different types of API interfaces for SRaaS depending on the overall deployment method. These are defined in the following examples:.

In a first example, the SRaaS <NUM> can be used as the centralized SDN controller for a full segment routing environment. In this case, the controller (SRaaS) <NUM> maintains the underlying segment routing topology and provides the necessary mechanisms to talk to the devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> encompassed therein. In this scenario, the SRaaS application <NUM> has to have direct access to the devices to push out the segment routing rules based on tenant and/or provider <NUM> input. The direct access could be in the form of netconf, RESTful APIs or any other configuration protocol supported on the underlying infrastructure devices. The above approach defines the south-bound API interfaces for the SRaaS <NUM>. North-bound, the service has to be able to receive commands from the tenants, any other application running within a tenant environment and the provider itself. The north-bound API is the same for both proposed deployments and is therefore outlined in a third example below.

In a second example, the inventors envision the deployment of the SRaaS <NUM> on top of an already existing segment routing environment. Here, the SRaaS <NUM> provides a layer between the tenant, provider application of a cloud provider and a segment routing controller. Southbound, the SRaaS application <NUM> provides RESTful APIs to talk to the segment routing controller (for example OPENDAYLIGHT or ONOS, etc.). The inventors believe this can be advantageous as segment routing deployments can be deployed independently of cloud environments and therefore might not rely on SRaaS <NUM> as the centralized controller but rather have an independent controller for broader purposes. As mentioned in the first example above, the north-bound APIs can be the same in both scenarios. In the third example below, north-bound API support is envisioned.

In the third example, the inventors envision the SRaaS <NUM> providing a north-bound API for tenants, their applications and providers to leverage the functionality of SRaaS <NUM>. The API is rich enough to allow a tenant and its application to either manually (the tenant administrator for example) or automatically (the tenant application) to send and receive API requests from the SRaaS <NUM> to define the underlying segment routing environment based on their specific needs. For example, the application may need a large amount of data retrieved from a database and thus need at an initialization stage a large amount of bandwidth, after which the bandwidth requirement diminishes. Here, the API may support tenant and tenant application separation to distinguish RESTful API calls. A tenant could, for example, define boundaries in the segment routing environment such that its application can automatically define routes based on its own requirements. The application should be able to access a set of API calls allowing the definition of forwarding rules to build the segment routing based table from its origin to destination. The provider can use the north-bound APIs to administratively define environmental settings (tenant privileges, SR configuration parameters, SR link characteristics, etc.).

Based on the above examples, the SRaaS <NUM> can maintain a local database for the configurations done by the tenant, its application and/or the providers. This is valuable to maintain a sync-able state between the SRaaS <NUM> and the underlying segment routing environment in case of a failure.

In another aspect, the inventors propose the usage of pricing details within the SRaaS application <NUM>. The pricing could be used by the provider and the tenant to base their segment routing forwarding definition on price related information. Here, a provider could, for example, define certain price details for certain links or forwarding rules. The tenant, defining the segment routing based overlay, can use the information to dynamically and on-demand modify forwarding decisions based on pricing provided. For example, if a higher bandwidth is needed for an application, the tenant can see the pricing for the increased bandwidth and in an on-demand manner, modify the forwarding decisions and pay that price for the enhanced service. This will enrich both the SRaaS application <NUM> itself but also provides flexibility to both the cloud provider and the tenants and allow for dynamically and very customizable adjustments to the segment routing overlay. Such decisions may also be governed by service level agreements for the tenant and service level agreements or policies governing the cloud environment.

<FIG> illustrates a method example. In this example, the SRaaS <NUM> is the entity that is performing the steps outlined in <FIG>. However, other examples could include the IP environment <NUM> also performing the steps or complimentary steps. The method includes receiving a configuration of an internet protocol environment (<NUM>), such as IP environment <NUM>. The configuration can include the layer <NUM> environment in a cloud provider or can include data across multiple cloud providers. The information provided can be dynamically adjusted based on current needs and available resources. The configuration defines the routing, forwarding, and/or paths used for two different nodes or entities <NUM>, <NUM> to communicate. As a first entity <NUM> and a second entity <NUM> communicate, network issues such as latency, jitter, bandwidth or throughput issues, packet loss, connectivity issues, etc., can affect the quality and efficiency of the communication. The configuration can be any data that defines or characterizes the forwarding between node <NUM> and node <NUM>. Based on that input to the SRaaS <NUM>, the system defines the forwarding paths. The tenant who desires to have workload processed in the environment <NUM> can provide data and provide an optimal of preferred path that the application will need to send data from node <NUM> to node <NUM> (which correspond respectively to node <NUM> and <NUM>).

Next, the method includes receiving a parameter associated with a workload of a tenant (<NUM>). In this example, the tenant can provide data or requirements such as its workload should have the best path to meet a certain requirement. The tenant could rely on the standard routing algorithms which can provide a potentially best route or pathway. The tenant can provide service level agreement (SLA) requirements which can automatically require a "best service" or other criteria. Thus, the tenant specifies specific parameters/SLA requirements/general requirements, etc., that the SRaaS <NUM> uses to define routing rules according to segment routing principles.

The method includes, based on the configuration and the parameter, generating tenant-defined layer <NUM> overlay segment routing rules that define how the workload of the tenant will route data in the internet protocol environment using segment routing (<NUM>). The SRaaS <NUM> defines what paths meet the requirement in segment routing. This approach allows for a software-defined network to manage segment routing so it can modify the forwarding of data based on various criteria. The resulting tenant-defined layer <NUM> overlay can choose the pathway between node <NUM> and node <NUM>. The result is the ability to implement per tenant or a per application/workload routing definition. The cloud service provider can also provide the routing definition, or in the alternative, the cloud service provider and the tenant can jointly define the routing definition by each providing, for example, requirement parameters and optional parameters and the SRaaS <NUM> can negotiate the various requirements and output the partially provider defined and partially tenant defined layer <NUM> overlay <NUM>.

In one example of the concepts disclosed herein, assume an optimal path is identified between node <NUM> and <NUM>. However, the path at some point fails to provide the best throughput because peak usage of the compute environment is currently happening. The load is high, and the tenant or application should adjust the routing environment while taking into account something else or other environment characteristics. The system provides for feedback to the SRaaS <NUM> to enable such timing-based dynamic changes to the layer <NUM> overlay. In such cases, the SRaaS <NUM> can dynamically adjust the tenant-defined layer <NUM> overlay and thus change the routing rules and/or forwarding paths. In another example, there can be a degradation of the compute environment in some areas, this can also cause the system to re-route or revise the protocol and avoid the problem regions.

The present disclosure provides a novel feature of establishing and modifying, in real-time and optionally based on certain thresholds such as certain levels of utilization and using the SRaaS <NUM>, the layer <NUM> overlay used for segment routing. Generating the tenant-define layer <NUM> overlay segment rules may replace existing segment routing rules. This approach gives tenants more control of how their workload is processed. In one aspect, this approach does not require nor care about the particular IP rules <NUM>, as the segment routing can control the routing requirements. Thus, if the cloud environment available to the tenant is a connected cloud A and cloud B, or some other type of environment that the system provides to the tenant, it will not matter in that the tenant can specify and communicate its requirements and thresholds to the SRaaS <NUM>. The system may require an extra cost for the ability of the tenant to provide their parameters and access the dynamic, real-time modification feature of the SRaaS <NUM>.

The configuration of environment <NUM> can be generated using an interior gateway protocol and represents a layer <NUM> environment. The interior gateway protocol can provide RIB details, link costs, metrics, router capability, shortest path to infrastructure points, etc. The parameter provided to SRaaS <NUM> by the tenant can include one or more of a tenant-defined layer <NUM> connectivity, a service level agreement, a specific resource capability, a per-application parameter, a timing parameter, a cost parameter, etc..

The present examples are to be considered as illustrative and not restrictive, and the examples is not to be limited to the details given herein, but may be modified within the scope of the appended claims.

Claim 1:
A method, at a Segment Routing as a Service, SRaaS, application (<NUM>), comprising:
receiving (<NUM>) a configuration of an internet protocol environment (<NUM>);
after receiving the configuration, receiving (<NUM>) a parameter associated with a workload of a tenant;
generating (<NUM>), based on the configuration and the parameter, tenant-defined layer <NUM> overlay segment routing rules that define how the data for the workload of the tenant will be routed in the internet protocol environment using segment routing;
causing the data for workload of the tenant to be routed in the internet protocol environment using segment routing in accordance with the tenant-defined layer <NUM> overlay segment routing rules by pushing out the routing rules to devices of the internet protocol environment;
receiving feedback associated with the tenant-defined layer <NUM> overlay segment routing rules, the feedback including rates of change of one or more factors within the environment and/or specifically related to the workload;
selecting, based on the rates of change, a time in which to dynamically modify the overlay and adjust the segment routing of the environment; and
updating the routing rules based on the feedback.