Automatic onboarding, management, and control across heterogeneous edge devices of a client network using device abstractions may be performed (e.g., different types of edge devices manufactured by different vendors). A device onboarding and integration service may emulate, by a first device abstraction, an edge device of a client network, where the edge device is a first type of device. The service emulates, by a second device abstraction, the edge device as a second type of edge device (e.g., from a different vendor/uses a different API). The service updates a state of the first device abstraction based on a state of the edge device. The service then updates a state of the emulating, by a second device abstraction, the edge device as a second type of edge device. The second device abstraction sends its updated state to an application at the client network.

Automatic onboarding, management, and control across heterogeneous edge devices of a client network using device abstractions may be performed (e.g., different types of edge devices manufactured by different vendors). A device onboarding and integration service may emulate, by a first device abstraction, an edge device of a client network, where the edge device is a first type of device. The service emulates, by a second device abstraction, the edge device as a second type of edge device (e.g., from a different vendor/uses a different API). The service updates a state of the first device abstraction based on a state of the edge device. The service then updates a state of the emulating, by a second device abstraction, the edge device as a second type of edge device. The second device abstraction sends its updated state to an application at the client network.

The present technology is directed to generating a common Border Gateway Protocol (BGP) attribute, for example, BGP-Slice Identifier (ID) for a specific network slice and stitching the network slice across one or more domains to realize end-to-end slicing. The present technology can generate BGP ID for a specific network slice spanning a plurality of domains and map domain-specific attributes associated with sub-slices of the specific network slice in different domains of the plurality of domains to the BGP ID. The present technology can further facilitate distribution of the mapping of the domain-specific attributes to the BGP ID across the plurality of domains for stitching the sub-slices together from the domain-specific attributes based on the BGP ID to stitch the specific network slice across the plurality of domains. Furthermore, the present technology can identify a configuration error in the mapping of the domain-specific attributes and the BGP ID and transmit a feedback informing the existence of the error for performing remedial measures.

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate, and provides an apparatus and a method for transmitting service provisioning information to a UE when the UE is in a reachable state. An operation method of a policy control function (PCF) entity includes: receiving a data management message including a service parameter generated by an application function (AF) entity from a network exposure function (NEF) entity; transmitting an N1N2 message indicating to transmit the service parameter to a user equipment (UE) to an access and mobility management function (AMF) entity; receiving, from the AMF entity, a transfer result message indicating whether the service parameter has been transmitted to the UE; and transmitting the transfer result message to the AF entity.

The present disclosure is generally related to edge computing technologies (ECTs), communications networking, network slicing, and in particular, to techniques and technologies for providing flow-specific network slices. In particular, the present disclosure describes mechanisms that expand existing end-to-end architectures in order to include quality of service and monitoring mechanisms that connect network slicing technologies with infrastructure and/or network data center quality of service provider domains. The described mechanisms provide data center bridging to enable network, edge computing, and cloud computing domains.

Methods, systems and apparatuses to enable an optimum bin selection by implementing a neural network with a network scheduling and configuration tool (NST), the method includes: configuring an agent with a critic function from neural networks wherein the agent neural network represents each bin of the collection of bins in the network that performs an action, and a critic function evaluates a criteria of success for performing the action; processing, by a scheduling algorithm, the VLs by the NST; determining one or more reward functions using global quality measurements based on criteria comprising: a lack of available bins, a lack of available VLs, and successfully scheduling operations of a VL into a bin; and training the network based on a normalized state model of the scheduled network by using input data sets to arrive at an optimum bin selection.

The current document is directed to methods and subsystems that instantiate and manage mobile-network computational infrastructure. The currently disclosed improved mobile-network-computational-infrastructure orchestration system employs several layers of containerized-application orchestration and management systems. For increased efficiency and security, mobile-network-specific operators are added to the containerized-application orchestration layers in order to extend the functionalities of the containerized-application orchestration layers and move virtualization-layer dependencies from the mobile-network-computational-infrastructure orchestration system down into the containerized-application orchestration layers. The improved mobile-network-computational-infrastructure orchestration system is responsible for generating, from an input mobile-network computational-infrastructure specification, one or more workload resource specifications and a node policy that are input to a containerized-application-orchestration layer. The containerized-application-orchestration layers instantiate and manage worker nodes that execute mobile-network application instances that implement VNFs and CNFs according to the one or more workload resource specifications and the node policy.

A model-driven system automatically deploys a virtualized service, including multiple service components, on a distributed cloud infrastructure. A master service orchestrator causes a cloud platform orchestrator to retrieve a cloud services archive file, extract a cloud resource configuration template and create cloud resources at appropriate data centers as specified. The master service orchestrator also causes a software defined network controller to retrieve the cloud services archive file, to extract a cloud network configuration template and to configure layer 1 through layer 3 virtual network functions and to set up routes between them. Additionally, the master service orchestrator causes an application controller to retrieve the cloud services archive file, to extract a deployment orchestration plan and to configure and start layer 4 through layer 7 application components and bring them to a state of operational readiness.

A method for correlating discarded network traffic with network policy events in a network includes receiving a flow record. The flow record includes initial network flow information in a standard flow record format. Discarded network traffic information associated with each network policy is received from a network policy enforcement device. Network traffic is discarded based on a network traffic policy. The received flow record is correlated with the received discarded network traffic information. The discarded network traffic information is encoded into the received flow record based on the correlation while maintaining the initial network flow information to yield an enhanced flow record.

A software defined networking (SDN) controller for a communication network is provided. The SDN controller includes a northbound interface, a southbound interface, and a database as a service (DBaaS) layer. The northbound interface includes an application layer having one or more independent SDN applications. The southbound interface includes an adapter layer having one or more independent device adapters. The DBaaS layer includes a persistent DBaaS unit and a state DBaaS unit.