An example communication method includes that a first terminal device receives through a first path a first data packet from a second terminal device. The first terminal device receives through a second path a second data packet from a second terminal device, where the first path has a mapping relationship with the second path. The first terminal device transmits, based on the mapping relationship, the first data packet and the second data packet to a same aggregation protocol layer entity to perform data aggregation processing.

A layer-based method and system for defining and enforcing policies in an information technology (IT) environment. Specifically, the disclosed method and system propose and implement a layer-based infrastructure management model, which partitions the scope and problem set of application and operational policy definition and/or enforcement into a hierarchy of abstraction layers.

Disclosed are systems and devices for interfacing media access tuning circuitry that implements collision handling or traffic shaping with a reduced media independent interface (RMII). In some embodiments, an interface circuitry manages emulated signals generated by a media access tuning circuitry in response to detecting that the emulated signals would cause incorrect operation of an RMII. Also disclosed is a physical layer (PHY) device for a multidrop network. In some embodiments the PHY device implements physical layer collision techniques and operable to communicate with a media access control (MAC) device via an RMII, where the MAC is configured for carrier-sense multiple access (CSMA), CSMA with collision detection (CSMA/CD), or CSMA with collision avoidance (CSMA/CA). Also disclosed are processes for managing signaling at a PHY that implements physical layer collision avoidance (PLCA) or traffic shaping, as the case may be.

Technologies for allocating resources across data centers include a compute device to obtain resource utilization data indicative of a utilization of resources for a managed node to execute a workload. The compute device is also to determine whether a set of resources presently available to the managed node in a data center in which the compute device is located satisfies the resource utilization data. Additionally, the compute device is to allocate, in response to a determination that the set of resources presently available to the managed node does not satisfy the resource utilization data, a supplemental set of resources to the managed node. The supplemental set of resources are located in an off-premises data center that is different from the data center in which the compute device is located. Other embodiments are also described and claimed.

Technologies for allocating resources across data centers include a compute device to obtain resource utilization data indicative of a utilization of resources for a managed node to execute a workload. The compute device is also to determine whether a set of resources presently available to the managed node in a data center in which the compute device is located satisfies the resource utilization data. Additionally, the compute device is to allocate, in response to a determination that the set of resources presently available to the managed node does not satisfy the resource utilization data, a supplemental set of resources to the managed node. The supplemental set of resources are located in an off-premises data center that is different from the data center in which the compute device is located. Other embodiments are also described and claimed.

This disclosure describes techniques for providing multiple namespace support to application(s) in containers under Kubernetes without breaking containment boundaries or escalating privileges of the application(s). A namespace service executing on a physical server may communicate with contained processes executing on the physical server by utilizing a Unix Domain Socket (UDS) endpoint in the filesystem of each of the containers. the namespace service may execute on the physical server with escalated privileges, allowing the namespace service to create a socket in a namespace and provide access and rights to utilize the socket to process(es) in a separate namespace.

An electronic device configured for electronic communications utilizing virtual dispersive networking includes: a network interface for communicating over a network; an application loaded onto the electronic device programmed to communicate over a network; and virtual dispersive networking software configured to create, for such application, a virtual machine comprising a virtual interface for the network interface of the electronic device; select a network protocol out of a plurality of available network protocols based on current communication requirements of the application; and cause network communications of the application to occur via the virtual network interface of the electronic device using the determined network protocol.

Datalink frames or networking packets contain protocol information in the header and optionally in the trailer of a frame or a packet. We are proposing a method in which part of or all of the protocol information corresponding to a frame or a packet is transmitted separately in another datalink frame. The Separately Transmitted Protocol Information is referred to as STPI. The STPI contains enough protocol information to identify the next hop node or port. STPI can be used avoid network congestion and improve link efficiency. Preferably, there will be one datalink frame or network packet corresponding to each STPI, containing the data and the rest of the protocol information and this frame/packet is referred to as DFoNP. The creation of STPI and DFoNP is done by the originator of the frame or packet such as an operating system.

Data is received at a buffer used by a protocol processing stack which protocol processes the received data. The received data is made available to, for example, an application, before the protocol processing of the data is complete. If the protocol processing is successful, the data made available to the application is committed.

In one embodiment, a method according to the present disclosure includes receiving a topology change advertisement at a remote core edge node and performing a network address information removal operation. The topology change advertisement is received from a core edge node that is in communication with an access network. The topology change advertisement indicates that a topology change has occurred in the access network. The network address information removal operation removes network address information stored by the remote core edge node. The network address information is used by the remote core edge node in participating in communications with the core edge node.