In an aspect, an embodiment of the present disclosure is directed to network control topology that implements a centralized network controller to deterministically assign, and reassign, underlay multicast groups according to one or more policies and/or parameterized intent of the network administrator. The centralized network controller, in some embodiments, comprises a map server-neap resolver controller configured to provide deterministic and centralized allocation of underlay multi cast groups, e.g., to provide security, traffic engineering, network and resource management.

In one embodiment, resource availability reallocation is used in establishing one or more new designated multicast flow paths with guaranteed availability of resources currently allocated and/or used by one or more designated existing multicast flow path to allocate/use for the new designated flow path(s). These resources typically include allocated guaranteed bandwidth of a network path between two adjacent or non-adjacent nodes of the network, and possibly forwarding/processing/memory resources of a network node. One embodiment communicates multicast control messages between nodes identifying to establish a new multicast flow path with resource availability reallocation from a designated multicast flow path. In one embodiment, a Protocol Independent Multicast-Sparse Mode (PIM-SM) Join/Prune Message identifies Pruning of one or more multicast flow paths and Joining of one or more different multicast flow paths and designating resource availability reallocation from these Pruned multicast flow path(s) to these Joined multicast flow path(s).

This application provides a channel access indication method and device. The method includes: receiving, by a first communications device, a channel synchronization request sent by a second communications device, where the channel synchronization request is used to request the first communications device to send a synchronization frame to the second communications device, and a wake-up receiver is configured for the second communications device; and according to the channel synchronization request and a time at which the second communications device is woken up and that is learned by the first communications device based on preset signaling, sending, by the first communications device when a channel is idle, the synchronization frame to the woken-up second communications device, where the synchronization frame is used to instruct the woken-up second communications device to access the channel after receiving the synchronization frame.

This disclosure describes an architecture for supporting MBS sessions in a wireless access network. Each of such MBS sessions is flexibly and dynamically delivered by the access network into one or more Point-To-Point (PTP, or unicast) and Point-To-Multipoint (PTM, or multicast) delivery instances. As such, a subset of the UEs participating in the MBS may be configured to receive the MBS session in a PTP-like manner and quality. The architecture further allows for access network level switching of one or more of the UEs participating in the MBS session between the PTP mode and PTM mode. Such switching are effectuated dynamically without involvement of application layer. The resource allocations and configuration for the PTP and PTM delivery instances may be performed in the access network collaboratively between a central unit (CU) and one or more distributed units (DUs). Such collaborative resource allocation and configuration may be effectuated using a novel architecture for the signaling messages between the CU and the DUs.

A method of transmitting multicast traffic to workloads of tenants communicating over overlay networks provisioned on top of a physical network includes the steps of: detecting the multicast traffic; determining that the multicast traffic is bound for workloads of a first tenant and workloads of a second tenant; encapsulating one instance of the multicast traffic using a Layer 2 (L2) over Layer 3 (L3) encapsulation protocol to generate encapsulated traffic, wherein the encapsulated traffic includes an identifier of a first backplane network corresponding to the first tenant and an identifier of a second backplane network corresponding to the second tenant in a header portion of each packet of the encapsulated traffic; and transmitting, to a first host computing device, the encapsulated traffic with the identifiers of the first and second overlay networks.

A method and apparatus include determining for use with a user equipment a measurement configuration, which includes at least information on a frequency location of synchronization signals, a carrier frequency value, and a measurement bandwidth. The measurement configuration is transmitted to the user equipment by higher layer signaling, where the higher layer signaling is above the physical layer. One or more synchronization signals are transmitted on the frequency location, from which a first identity value can be determined. A broadcast channel is transmitted to the user equipment from which a second identity value can be determined, the broadcast channel including a first reference signal based on the first identity value. A second reference signal based on the first identity value, the second identity value, the frequency location of synchronization signals, the carrier frequency value, and the measurement bandwidth is transmitted.

A network device configured to perform scalable, in-network computations is described. The network device is configured to process pull requests and/or push requests from a plurality of endpoints connected to the network. A collective communication primitive from a particular endpoint can be received at a network device. The collective communication primitive is associated with a multicast region of a shared global address space and is mapped to a plurality of participating endpoints. The network device is configured to perform an in-network computation based on information received from the participating endpoints before forwarding a response to the collective communication primitive back to one or more of the participating endpoints. The endpoints can inject pull requests (e.g., load commands) and/or push requests (e.g., store commands) into the network. A multicast capability enables tasks, such as a reduction operation, to be offloaded to hardware in the network device.

The techniques describe example network systems for adaptively determining whether to perform ingress replication or assisted replication of a multicast flow based on classification of the multicast flow. For example, a provider edge (PE) device of a plurality of PE devices participating in an EVPN comprises one or more processors operably coupled to a memory, wherein the one or more processors are configured to: receive a multicast traffic flow, determine a classification of the multicast traffic flow, and perform, based at least in part on the classification of the multicast traffic flow, one of: ingress replication of the multicast traffic flow or assisted replication of the multicast traffic flow.

In an aspect, an embodiment of the present disclosure is directed to network control topology that implements a centralized network controller to deterministically assign, and reassign, underlay multicast groups according to one or more policies and/or parameterized intent of the network administrator. The centralized network controller, in some embodiments, comprises a map server-map resolver controller configured to provide deterministic and centralized allocation of LISP underlay multicast groups, e.g., to provide security, traffic engineering, network and resource management.

Disclosed is a computer network including a group of a plurality of computing resource infrastructures associated with a plurality of orchestrators responsible for allocating the resources of this infrastructure to one or more client applications and grouped into a swarm in which they are interconnected by a cooperation interface, the allocation of resources being decided by a decision method based firstly on evaluations distributed among the orchestrators, then on a consensus protocol between the orchestrators which is based on the evaluations and is carried out at the cooperation interface in order to choose one of the infrastructures of the group to host some or all of the client application.