Patent classifications
H04L41/5096
MANAGEMENT AND ORCHESTRATION OF HETEROGENEOUS NETWORK ENVIRONMENT USING DYNAMIC, ROBUST AND NETWORK AWARE MICROSERVICES
State of the art networking solutions are tightly coupled and proprietary in nature due to multiple vendors in the networking domain. Embodiments of the present disclosure provide a method and system for management and orchestration of heterogeneous network environment using dynamic, robust and network aware microservices. The method enables a platform for automatically and dynamically identifying appropriate group of microservices in accordance with network type and service type specified by the user, thus providing a solution that generates network aware microservices for each network in the heterogeneous network landscape. Furthermore, the system manages the identified microservices for each of the network by managing the life cycle of these microservices. The right life cycle management and coordination of the microservices for the network is in-line with desired goals/business logic, in a reliable and scalable manner, in heterogeneous network environments.
ANOMALY DETECTION USING TENANT CONTEXTUALIZATION IN TIME SERIES DATA FOR SOFTWARE-AS-A-SERVICE APPLICATIONS
A system may include a historical time series data store that contains electronic records associated with Software-as-a-Service (“SaaS”) applications in a multi-tenant cloud computing environment (including time series data representing execution of the SaaS applications). A monitoring platform may retrieve time series data for the monitored SaaS application from the historical time series data store and create tenant vector representations associated with the retrieved time series data. The monitoring platform may then provide the retrieved time series data and tenant vector representations together as final input vectors to an autoencoder to produce an output including at least one of a tenant-specific loss reconstruction and tenant-specific thresholds for the monitored SaaS application. The monitoring platform may utilize the output of the autoencoder to automatically detect an anomaly associated with the monitored SaaS application.
IDENTIFYING MOBILE DEVICE LOCATION AND CORRESPONDING SUPPORT CENTER LOCATIONS TO PROVIDE SUPPORT SERVICES OVER A NETWORK
A mobile device may receive updates, support and other data from a current data center agent platform. When the mobile device travels to another location the nearest data center agent may be different from the previous agent. A changeover determination must be performed prior to determining whether the new agent should be assigned to the mobile device. One example method of operation may include receiving current location information of the mobile device and identifying a present location of the mobile device and a current service center assigned to the mobile device. The method may also provide determining whether a new service center location at a remote location from the current service center location should be assigned to the mobile device based on predefined assignment criteria.
NEAR-REAL-TIME AND REAL-TIME COMMUNICATIONS
The present disclosure generally discloses capabilities for supporting new network zones and associated services. The network zones and associated services may include a near-real-time (NRT) zone and associated NRT services, a real-time (RT) zone and associated RT services, or the like. The resilient network zones and associated resilient and non-resilient services may be configured to provide bounded latency guarantees for reliably supporting various types of applications (e.g., mobile fronthaul, cloud computing, Internet-of-Things (IoT), or the like). The network zones and associated services may be provided using a distance-constrained fiber and wavelength switching fabric design comprised of various network devices and using associated controllers, which may be configured to support service provisioning functions, service testing functions, wavelength switching functions, and so forth.
Remote port for network connectivity for non-colocated customers of a cloud exchange
In general, techniques are described for network connectivity for non-colocated customers of a cloud exchange. A programmable network platform for the cloud exchange comprises processing circuitry configured to: configure a virtual network device in the data center to run a network service for a customer; receive, from the customer, a request for a remote port and network information for a network service provider connectivity service for the customer; assign, in response to receiving the request for the remote port, a remote port of the cloud exchange to the customer; and configure, in response to receiving the request for the remote port using the network information, the cloud exchange to connect the network service provider connectivity service to the virtual network device via the remote port of the cloud exchange.
INDUSTRIAL SETUP COMPOSITION
Technical solutions are described for selecting components from multiple vendors for a system. An example computer-implemented method includes receiving, by a processor, an environment map that identifies a first component placeholder of the system. The computer-implemented method further includes identifying, by the processor, that the first component placeholder interfaces with a second component placeholder of the system. The computer-implemented method further includes determining, by the processor, a role assigned to the first component placeholder, where the role indicates a type of data that a first component at the first component placeholder communicates with a second component at the second component placeholder. The computer-implemented method further includes determining, by the processor, a list of components for selecting the first component, where each component from the list of components matches the role assigned to the first component placeholder.
SYSTEM AND METHOD FOR GLOBAL DATA SHARING
Sharing data in a data exchange across multiple cloud computing platforms and/or cloud computing platform regions is described. An example method can include generating a consumer account corresponding to a first cloud entity and receiving, by the first cloud entity, a copy of a data set from a provider account corresponding to a second cloud computing entity, wherein the first cloud computing entity and the second cloud computing entity represent different regions of a cloud computing platform. The method may also include accessing, by the consumer account, the copy of the data set.
TECHNIQUES FOR IMPLEMENTING ROLLBACK OF INFRASTRUCTURE CHANGES IN A CLOUD INFRASTRUCTURE ORCHESTRATION SERVICE
Techniques for implementing rollback of infrastructure changes in an infrastructure orchestration service are described. In certain examples, an infrastructure orchestration service is disclosed that manages both provisioning and deploying of infrastructure assets within a cloud environment. The service receives a plan comprising a set of instructions associated with a set of infrastructure assets of an execution target and identifies a first state of the set of infrastructure assets. The service executes the set of instructions in the plan to achieve a second state for the set of infrastructure assets. Based in part on the executing, the service receives a trigger for rolling back the plan to restore the set of infrastructure assets in the plan to the first state and executes a rollback plan for the plan. The service then transmits a result associated with the execution of the rollback plan.
Database protocol for exchanging forwarding state with hardware switches
Some embodiments provide a set of one or more network controllers that communicates with a wide range of devices, ranging from switches to appliances such as firewalls, load balancers, etc. The set of network controllers communicates with such devices to connect them to its managed virtual networks. The set of network controllers can define each virtual network through software switches and/or software appliances. To extend the control beyond software network elements, some embodiments implement a database server on each dedicated hardware. The set of network controllers accesses the database server to send management data. The hardware then translates the management data to connect to a managed virtual network.
Systems and methods for cloud migration readiness
A method comprising discovering workload attributes and identify dependencies, receiving utilization performance measurements including memory utilization measurements of at least a subset of workloads, grouping workloads based on the workload attributes, the dependencies, and the utilization performance measurements into affinity groups, determining at least one representative synthetic workload for each affinity group, each representative synthetic workload including a time slice of a predetermined period of time when there are maximum performance values for any number of utilization performance measurements among virtual machines of that particular affinity group, determining at least one cloud service provider (CSP)'s cloud services based on performance of the representative synthetic workloads, and generating a report for at least one of the representative synthetic workloads, the report identifying the at least one of the representative synthetic workloads and the at least one CSP's cloud services including cloud workload cost.