Abstract: A system described herein may maintain records, in a distributed ledger, that include parameters (e.g., Quality of Service (“QoS”) parameters and/or Multi-Access/Mobile Edge Computing (“MEC”) device management parameters) that are associated with particular applications and/or MEC operator systems. The system may identify a particular record, from the distributed ledger, that is associated with a particular MEC operator system. The particular record may indicate a first set of MEC configuration parameters implemented by the MEC device operator system, and one or more triggers based on which the first set of MEC configuration parameters were implemented by the MEC device operator system. The system may record a set of modified application parameters, that are generated based on the identified first set of MEC configuration parameters and the one or more triggers, to the distributed ledger.

Abstract: A system described herein may monitor, on an ongoing basis, a Key Performance Indicators (“KPIs”) associated with a wireless network. The system may receive, from a particular device, a monitoring policy specifying one or more criteria, and may compare the criteria associated with the monitoring policy to the monitored KPIs. The system may determine, based on the comparing, that the criteria associated with the monitoring policy is satisfied; may determine a particular subset of the monitored KPIs based on the monitoring policy and further based on determining that the criteria associated with the monitoring policy is satisfied; and may output the particular subset of the monitored KPIs to the second device. The system may monitor the wireless network via private interfaces that are not exposed to devices external to the wireless network.

Abstract: A device may receive network data identifying key performance indicators associated with a base station and user equipment (UEs), UE data identifying UE data records and UE locations, and geographic data identifying a geographic area and features of the geographic area. The device may correlate the network data, the UE data, and the geographic data to generate correlated data. The device may process, the correlated data, with a plurality of machine learning models, to generate a corresponding plurality of results, and may evaluate the plurality of results, with prediction models, to generate a set of results. The device may compare classification cost function weighted predictions and the set of results to generate comparisons, and may select a machine learning model, for the geographic area and from the plurality of machine learning models, based on the comparisons. The device may implement the machine learning model for the geographic area.

Abstract: Systems and methods described herein provide dynamic orchestration of deep packet inspection (DPI) probes in a transport network. A network device receives an event report for a critical severity event in a network and stores the event report with other event reports to form an event data set. The network device correlates the event data set with a monitoring condition and selects a workflow for a DPI probe deployment that corresponds to the monitoring condition. The network device sends, to a service orchestrator device, a call to deploy a DPI probe in the network based on the workflow.

Abstract: A system described herein may monitor, on an ongoing basis, a Key Performance Indicators (“KPIs”) associated with a wireless network. The system may receive, from a particular device, a monitoring policy specifying one or more criteria, and may compare the criteria associated with the monitoring policy to the monitored KPIs. The system may determine, based on the comparing, that the criteria associated with the monitoring policy is satisfied; may determine a particular subset of the monitored KPIs based on the monitoring policy and further based on determining that the criteria associated with the monitoring policy is satisfied; and may output the particular subset of the monitored KPIs to the second device. The system may monitor the wireless network via private interfaces that are not exposed to devices external to the wireless network.

Abstract: A system described herein may monitor, on an ongoing basis, a Key Performance Indicators (“KPIs”) associated with a wireless network. The system may receive, from a particular device, a monitoring policy specifying one or more criteria, and may compare the criteria associated with the monitoring policy to the monitored KPIs. The system may determine, based on the comparing, that the criteria associated with the monitoring policy is satisfied; may determine a particular subset of the monitored KPIs based on the monitoring policy and further based on determining that the criteria associated with the monitoring policy is satisfied; and may output the particular subset of the monitored KPIs to the second device. The system may monitor the wireless network via private interfaces that are not exposed to devices external to the wireless network.

Abstract: A system described herein may maintain records, in a distributed ledger, that include parameters (e.g., Quality of Service (“QoS”) parameters and/or Multi-Access/Mobile Edge Computing (“MEC”) device management parameters) that are associated with particular applications and/or MEC operator systems. The system may identify a particular record, from the distributed ledger, that is associated with a particular MEC operator system. The particular record may indicate a first set of MEC configuration parameters implemented by the MEC device operator system, and one or more triggers based on which the first set of MEC configuration parameters were implemented by the MEC device operator system. The system may record a set of modified application parameters, that are generated based on the identified first set of MEC configuration parameters and the one or more triggers, to the distributed ledger.

Abstract: A system described herein may record, to a distributed ledger, information associating a particular application with a particular set of Quality of Service (“QoS”) information. A particular Multi-Access/Mobile Edge Computing (“MEC”) device operator system may access the distributed ledger to identify the information associating the particular application with the particular set of QoS information. The system may read, from the distributed ledger, MEC configuration information indicating that the MEC device operator system has configured one or more MEC devices, of a plurality of MEC devices to provide the particular application in accordance with the particular set of QoS information. The system may select a particular MEC device, from the plurality of MEC devices, based on a request and further based on the MEC configuration information, and may output an indication of the selected particular MEC device in response to the request.

Abstract: A device may receive a consent address from a user device accessing an application that requires application data associated with consent of a user of the user device, and may provide, to the user device, a consent form associated with the consent address. The device may receive, from the user device, user authentication data provided via the consent form and via a first option or a second option, and may provide, to an application server device associated with the application, a notification indicating that the user authentication data was received. The device may provide, to a cloud service provider web services device, an authorization code and an authorization token based on providing the notification. The cloud service provider web services device may cause the application data to be provided to the application server device based on receiving the authorization code and the authorization token.

Abstract: A device may receive a protocol data unit session anchor (PSA) failure alarm associated with a first PSA at a first site with a first edge device, and may receive a PSA active alarm associated with a second PSA at a second site. The device may receive latency data identifying a latency between the first site and the second site, and may determine a failover from the first PSA to the second PSA based on the PSA failure alarm and the PSA active alarm. The device may identify an optimal edge device for the second PSA based on the latency data, and may generate a notification identifying the optimal edge device and the second PSA. The device may provide the notification to a user equipment affected by the failover from the first PSA to the second PSA.

Abstract: A method for managing an initiation of a computing system. In an embodiment, the method includes a computer processor detecting that a first computing system receives a request to initiate a second computing system. The method further includes accessing a table that includes information associated with a plurality of storage entities that include bootable OS images, where the plurality of storage entities are included in at least one storage system. The method further includes determining a first storage entity that includes a corresponding instance of a first bootable OS image of the requested second computing system. The method further includes initiating the requested second computing system based, at least in part, on the instance of the bootable OS image of the first storage entity.

Abstract: A method for managing an initiation of a computing system. In an embodiment, the method includes a computer processor detecting that a first computing system receives a request to initiate a second computing system. The method further includes accessing a table that includes information associated with a plurality of storage entities that include bootable OS images, where the plurality of storage entities are included in at least one storage system. The method further includes determining a first storage entity that includes a corresponding instance of a first bootable OS image of the requested second computing system. The method further includes initiating the requested second computing system based, at least in part, on the instance of the bootable OS image of the first storage entity.

Abstract: A method for managing an initiation of a computing system. In an embodiment, the method includes a computer processor detecting that a first computing system receives a request to initiate a second computing system. The method further includes accessing a table that includes information associated with a plurality of storage entities that include bootable OS images, where the plurality of storage entities are included in at least one storage system. The method further includes determining a first storage entity that includes a corresponding instance of a first bootable OS image of the requested second computing system. The method further includes initiating the requested second computing system based, at least in part, on the instance of the bootable OS image of the first storage entity.

Abstract: A method for managing an initiation of a computing system. In an embodiment, the method includes a computer processor detecting that a first computing system receives a request to initiate a second computing system. The method further includes accessing a table that includes information associated with a plurality of storage entities that include bootable OS images, where the plurality of storage entities are included in at least one storage system. The method further includes determining a first storage entity that includes a corresponding instance of a first bootable OS image of the requested second computing system. The method further includes initiating the requested second computing system based, at least in part, on the instance of the bootable OS image of the first storage entity.

Abstract: A method for managing an initiation of a computing system. In an embodiment, the method includes a computer processor detecting that a first computing system receives a request to initiate a second computing system. The method further includes accessing a table that includes information associated with a plurality of storage entities that include bootable OS images, where the plurality of storage entities are included in at least one storage system. The method further includes determining a first storage entity that includes a corresponding instance of a first bootable OS image of the requested second computing system. The method further includes initiating the requested second computing system based, at least in part, on the instance of the bootable OS image of the first storage entity.

Abstract: A method for managing an initiation of a computing system. In an embodiment, the method includes a computer processor detecting that a first computing system receives a request to initiate a second computing system. The method further includes accessing a table that includes information associated with a plurality of storage entities that include bootable OS images, where the plurality of storage entities are included in at least one storage system. The method further includes determining a first storage entity that includes a corresponding instance of a first bootable OS image of the requested second computing system. The method further includes initiating the requested second computing system based, at least in part, on the instance of the bootable OS image of the first storage entity.