A metrics collection method includes: transmitting a media data obtaining request to an application service device in response to a trigger operation for streaming media; obtaining a media data response message transmitted by the application service device, the media data response message including metrics collection configuration information, and the metrics collection configuration information including metrics collection environment information and network slice information; obtaining environment information of the streaming media, and when the environment information matches the metrics collection environment information, collecting metrics data corresponding to the streaming media; determining, based on the network slice information, a network path for reporting the metrics data; and reporting the metrics data to the application service device through the network path.

In some examples, a computing device may determine a prediction of a network outage of a network. The computing device may determine a priority of one or more data types expected to be received during the network outage. Further, the computing device may determine a latency category of the one or more data types expected to be received during the network outage. The computing device may store a data transmission rule for the one or more data types at least partially based on the priority and the latency category. The computing device may receive, from one or more data generators, during the network outage, data for transmission to the network. The computing device may transmit at least some of the received data to the network at least partially based on the data transmission rule.

A method includes polling, via a service specific manager operating on a software container in a cloud infrastructure, usage of different application resources and parameters for each service of a plurality of services provided in the cloud infrastructure to yield respective polled data for each service, collating, at the service specific manager, the respective polled data for each service to yield a collation, and based on the collation, deriving a respective weight for each service which a container manager can use to create multiple instances of a new service. The method further includes communicating the respective weight for each service to the container manager and determining, via the container manager, whether to scale up or scale down container services based on the respective weight for each service.

Techniques for configuring a network based on a Domain Name System (DNS) or network metadata policy for network control are disclosed. In some embodiments, a system, process, and/or computer program product for a DNS or network metadata policy for network control includes receiving a DNS or network metadata update at a DNS server (e.g., an authoritative or recursive DNS server) or an IP Address Management (IPAM) server, in which the DNS or network metadata update is determined to be relevant to the DNS or network metadata policy for network control; and sending the DNS or network metadata update to a network controller for a network, in which the network controller configures a plurality of network devices on the network based on the DNS or network metadata policy for network control.

The invention relates to a circuit board for a server system. The circuit board is adapted to be installed either in a server of a first type or in a server of a second type different from the first type. The circuit board comprises connections (A to H) for receiving assembly groups and a control. The control is adapted to show an order of the connections (A to H) depending on the types.

Techniques are disclosed for the identification of applications from communication sessions of network traffic between client devices and the generation of application-specific metrics for network traffic associated with the applications. In one example, a router obtains metrics for a plurality of packets. The router determines a session of a plurality of sessions associated with each packet. For each determined session, the router generates metrics for the session from the metrics of the packets associated with the session and determines an application of a plurality of applications associated with the session. For each determined application, the router generates metrics for the application from the metrics of the sessions associated with the application and transmits, to a device, the metrics for the application. In some examples, the router generates the metrics for each application on a per-client, per-next-hop, or per-traffic class basis.

Aspects of methods and systems for frequency multiplexing suitable for Data Over Cable Service Interface Specification (DOCSIS) are provided. A system for multiplexing signals according to frequency comprises a DOCSIS port interface, an upstream interface, a downstream interface, and a circulator subsystem. The DOCSIS port interface comprises a plurality of channel filters. The upstream interface is operably coupled to a first channel filter of the plurality of channel filters, and the downstream interface is operably coupled to a second channel filter of the plurality of channel filters. The circulator subsystem is able to direct a first signal from the upstream interface to the DOCSIS port interface and is able to direct a second signal from the DOCSIS port interface to the downstream interface.

In some examples, a method includes determining, with a Dynamic Host Configuration Protocol (DHCP) server, a primary Domain Name Service (DNS) server and a backup DNS server for a DHCP client in a network. In this method, the primary DNS server and the backup DNS server are automatically determined from a pool of DNS servers to provide a predetermined Quality of Experience (QoE) for the DHCP client based on dynamic network parameters of the network. The method can further include assigning, with the DHCP server, the primary and backup DNS servers to the DHCP client.

Provided are example methods and apparatus for orchestrating cloud computing resources which enable customizing cloud management software to add, via user-provided code, features and functionality which go beyond base features built into the cloud management software, without otherwise modifying the cloud computing management software. The user-provided code can include a plug-in, a script, a webhook, a callout, the like, or a combination thereof.

Controller(s) in a software defined network (SDN) are able to determine a control path towards each network switch by performing a switch-originated discovery and using an in-band control network that is an overlay on the data network. A topology tree is maintained, where each controller being the root of the tree, and where messages from the root to any switch may pass through neighboring switches to reach that switch (and vice-versa). Each switch in the SDN attempts to connect to the controller when it does not have a readily configured control connection towards the controller. Once the controller learns about the presence of a new switch and at least one or more paths to reach that switch through a novel discovery process, it can select, adjust and even optimize the control path's route towards that switch.