In general, the disclosure describes techniques for measuring edge-based quality of experience (QoE) metrics. For instance, a network device may construct a topological representation of a network, including indications of nodes and links connecting the nodes within the network. For each of the links, the network device may select a node device of the two node devices connected by the respective link to measure one or more QoE metrics for the respective link, with the non-selected node device not measuring the QoE metrics. In response to selecting the selected node device, the network device may receive a set of one or more QoE metrics for the respective link for data flows flowing from the selected node device to the non-selected node device. The network device may store the QoE metrics and determine counter QoE metrics for data flows flowing from the non-selected node device to the selected node device.

The present invention provides methods and apparatuses for service based architecture (SBA) for data analytics management (DAM). Configuration specifications are provided for configuring DAM entities for infrastructure management by infrastructure managers (InfMs), customer service managers (CSMs) for network slice subnet instance (NSSI), network slice instance (NSI) and service instance (SI) management, content and forwarding managers (CFM) for content and content cache management. Also provided are methods and apparatus for data analytics service provisioning regardless of DAM architecture.

The present invention provides methods and apparatuses for service based architecture (SBA) for data analytics management (DAM). Configuration specifications are provided for configuring DAM entities for infrastructure management by infrastructure managers (InfMs), customer service managers (CSMs) for network slice subnet instance (NSSI), network slice instance (NSI) and service instance (SI) management, content and forwarding managers (CFM) for content and content cache management. Also provided are methods and apparatus for data analytics service provisioning regardless of DAM architecture.

Described are examples for providing a system for managing configuration and policies for a virtualized wide area network (vWAN) support on a wide area network (WAN). The vWAN includes a plurality of virtual network entities associated with geographic locations including the physical computing resources of the WAN and virtual connections between the virtual network entities. The system includes a network safety component for managing configurations and policies of the vWAN on the WAN. The network safety component receives a change to a policy or configuration of the vWAN from an operator of a network connected to the vWAN. The network safety component evaluates a set of safety rules for the operator based on the change and a network state of a physical WAN underlying the vWAN. The network safety component generates an error message in response to at least one of the set of safety rules failing the evaluation.

A method for distributing network function (NF) high availability (HA) topology information in a core network includes, at an NF repository function (NRF) including at least one processor, receiving, from a plurality of producer NFs in an NF set, NFRegister requests including NF HA topology information for the producer NFs. The method further includes registering the producer NFs and storing the NF HA topology information for the producer NFs. The method further includes receiving, from a consumer NF or service communication proxy (SCP), an NFDiscover request containing at least one service discovery parameter that corresponds to a service provided by the producer NFs. The method further includes responding to the NFDiscover request by generating an NFDiscover response, including, in the NFDiscover response, the NF HA topology information for the producer NFs, and transmitting the NFDiscover response to the consumer NF or SCP.

To provide a low latency near RT RIC, some embodiments separate the RIC's functions into several different components that operate on different machines (e.g., execute on VMs or Pods) operating on the same host computer or different host computers. Some embodiments also provide high speed interfaces between these machines. Some or all of these interfaces operate in non-blocking, lockless manner in order to ensure that critical near RT RIC operations (e.g., datapath processes) are not delayed due to multiple requests causing one or more components to stall. In addition, each of these RIC components also has an internal architecture that is designed to operate in a non-blocking manner so that no one process of a component can block the operation of another process of the component. All of these low latency features allow the near RT RIC to serve as a high speed IO between the E2 nodes and the xApps.

Techniques described herein relate to a method for deploying workflows. The method may include receiving, at a service controller of a federated controller, a request to deploy a workflow in a device ecosystem; decomposing, by the service controller, the workflow into a plurality of workflow portions; performing, by the service controller, a search in a capabilities and constraints data construct to identify a domain in which to perform a workflow portion of the plurality of workflow portions; providing the workflow portion and workflow constraints to a platform controller in the domain; performing, by the platform controller, a subgraph similarity check to determine that a previously executed workflow portion was successfully executed on a subgraph in the domain; provisioning, by the platform controller, a set of devices in the domain based on the subgraph; and executing the workflow portion in the domain.

Various example embodiments for supporting communications management may be configured to support communications management for an operations technology (OT) domain that uses an associated network domain for supporting communications of the OT domain. Various example embodiments for supporting communications management for an OT domain that uses an associated network domain for supporting communications of the OT domain may be configured to support such communications management based on slice management capabilities. Various example embodiments for supporting communications management for an OT domain that uses an associated network domain for supporting communications of the OT domain, based on slice management capabilities, may be configured to support such communications management based on support for slice configuration across the OT domain and the network domain.

A system and a method for managing a virtual network function (VNF) and a multi-access edge computing (MEC) topology are provided. The method includes the following steps. A first VNF descriptor (VNFD) corresponding to a first VNF is received. According to the first VNFD, first provision data is generated. According to the first VNFD, first internal topology information of the first VNF is generated. According to the first provision data, the first VNF is instantiated to be provisioned. In response to provisioning the first VNF, a graphical user interface including the first internal topology information is output, and the first internal topology information includes a network component communicatively connected to the first VNF.

The current document is directed a resource-exchange system that facilitates resource exchange and sharing among computing facilities. The currently disclosed methods and systems employ efficient, distributed-search methods and subsystems within distributed computer systems that include large numbers of geographically distributed data centers to locate resource-provider computing facilities that match the resource needs of resource-consumer computing-facilities based on attribute values associated with the needed resources, the resource providers, and the resource consumers. The resource-exchange system monitors and controls resource exchanges on behalf of participants in the resource-exchange system in order to optimize resource usage within participant data centers and computing facilities. Virtual machines that provide the execution environment for multi-tiered applications described by hierarchically organized multi-tiered-application specifications are automatically distributed across one or more resource-provider-computing-facility hosts by the resource-exchange system.