Techniques for monitoring service availability using distributed Border Gateway Protocol (BGP) routing feeds are disclosed. In some embodiments, monitoring service availability using distributed BGP routing feeds includes collecting BGP routing data from a plurality of distributed route monitors; aggregating the collected BGP routing data into bins; and determining a BGP metric based on the aggregated and collected BGP routing data. Example BGP metrics include a reachability metric, number of path changes metric, and a number of BGP updates metric.

Multiple mobile cellular network (MCN) communication systems can be networked together to form a network of MCN communication systems (NOM). Each MCN communication system within the NOM can operate as an independent cellular network to provide communications between user equipment within a covered area. The MCN can be managed by a network management control center (NMCC). The NMCC can be configured generate coverage maps of the NOM and NMC system coverage areas.

Systems and methods for virtual network implementation and management based on a peer-to-peer metadata exchange are disclosed. Metadata pertaining to a flow traversing a virtual network overlaying an underlying network is generated in accordance with actions executed to send data packets via the underlying network relative to the virtual network. The metadata is encapsulated in one or more control packets sent to a set of nodes of the underlying network. Each node of the set of nodes maintains a copy of the metadata received in the one or more control packets in a local data store. The metadata is accessed via the local data store when needed to process packets of the flow.

The present application discloses a method and an apparatus for implementing an OAM function. In this solution, a unified OAM management center processes, based on a unified OAM management data model, network OAM status information, but the unified OAM management data model is unrelated to a network technology used by a network entity.

A spacecraft network management system includes five functional entities, namely, attendant, accessor, collector, logic, and logic watchdog in a distributed architecture configured with both in-band and out-of-band data paths. Management data is structured so that it can travel over either in-band or out-of-band and be identified as such; user data travels over in-band paths. These five entities are distributed over the units of the design and then a modified set of otherwise standard elements are assigned to each entity depending on the nature of its function. These elements include managers, management agents, device agents, device management information base, and manager management information base that enable the entities to perform their respective functions.

A spacecraft network management system includes five functional entities, namely, attendant, accessor, collector, logic, and logic watchdog in a distributed architecture configured with both in-band and out-of-band data paths. Management data is structured so that it can travel over either in-band or out-of-band and be identified as such; user data travels over in-band paths. These five entities are distributed over the units of the design and then a modified set of otherwise standard elements are assigned to each entity depending on the nature of its function. These elements include managers, management agents, device agents, device management information base, and manager management information base that enable the entities to perform their respective functions.

The present application relates to a mobile core network (MCN) supporting end-to-end (E2E) network slicing, which comprises a controlling entity (CA_NF), one or more network function (NF) entities extended with functionalities (CA-NFExt), a network management entity (OSS) extended with functionalities (CA_OSSExt), and a coordination entity (CA_CF). The CA_NF communicates with the CA_OSSExt through the CA_CF using interfaces (If-CA_MP and If-CAC_OSS), and with the CA-NFExts using a respective interface (If-CA_NF) and/or other NFs interfaces. Based on information received from the OSS and the NF entities, the CA_NF generates a context with a certain type, sends, based on the generated context, context-related information towards entities impacted by the generated context amongst the NF entities and the OSS, and blocks, for a period of time, a transmission of any generated context towards the NF entities upon receiving, from the OSS, a notification message once the OSS decides to enforce a change.

The present application relates to a mobile core network (MCN) supporting end-to-end (E2E) network slicing, which comprises a controlling entity (CA_NF), one or more network function (NF) entities extended with functionalities (CA-NFExt), a network management entity (OSS) extended with functionalities (CA_OSSExt), and a coordination entity (CA_CF). The CA_NF communicates with the CA_OSSExt through the CA_CF using interfaces (If-CA_MP and If-CAC_OSS), and with the CA-NFExts using a respective interface (If-CA_NF) and/or other NFs interfaces. Based on information received from the OSS and the NF entities, the CA_NF generates a context with a certain type, sends, based on the generated context, context-related information towards entities impacted by the generated context amongst the NF entities and the OSS, and blocks, for a period of time, a transmission of any generated context towards the NF entities upon receiving, from the OSS, a notification message once the OSS decides to enforce a change.

The methods, systems, and computer readable media discussed herein are directed to maintaining status information of network functions (NFs) associated with one or more network function repository functions (NRFs). An NRF, which may be one of a plurality of NRFs belonging to a group of NRFs, maybe queried. The plurality of NRFs may be synchronized to each other, and the group of NRFs may be one of a plurality of groups of NRFs. One or more NFs may be registered with the NRF, and each NRF of the plurality of NRFs may have one or more corresponding NFs registered to it. The NRF may maintain status information of the one or more NFs registered to the NRF. The NRF may collect information associated with querying of NFs by another NF, and send statistical data based on the collected information to a user interface (UI) of an external device to be displayed on the UI.

A system includes a software-defined wide area network having a software-defined wide area network control plane and a software-defined wide area network user plane; wherein the wide area network control plane is configured to operate in a first network and the wide area network user plane is configured to operate in a second network and further configured to communicate with the wide area network control plane, a serving gateway user plane in communication with the software-defined wide area network user plane, wherein the serving gateway user plane is configured to operate in the second network and further configured to communicate wirelessly with a device, and wherein the wide area network user plane is configured to route a communication between the device and a destination.