Abstract: In some implementations, a management system may receive service information from a plurality of service providers. A plurality of network devices, of the plurality of service providers, may be blockchain nodes of a blockchain. The service information, of a service provider, may identify network services provided by a network device of the service provider and identifies a location of the network device. The management system may receive, via the blockchain, information regarding a service-level agreement associated with a subset of service providers, of the plurality of service providers, providing network services for an application. The management system may receive, via the blockchain, an approval of the service-level agreement from each service provider of the subset of service providers. The management system may perform an action based on the service-level agreement and based on the network services provided by the subset of service providers for the application.

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: In some implementations, a management system may receive service information from a plurality of service providers. A plurality of network devices, of the plurality of service providers, may be blockchain nodes of a blockchain. The service information, of a service provider, may identify network services provided by a network device of the service provider and identifies a location of the network device. The management system may receive, via the blockchain, information regarding a service-level agreement associated with a subset of service providers, of the plurality of service providers, providing network services for an application. The management system may receive, via the blockchain, an approval of the service-level agreement from each service provider of the subset of service providers. The management system may perform an action based on the service-level agreement and based on the network services provided by the subset of service providers for the application.

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 first information associating Uniform Resource Locator (“URLs”) with respective Internet Protocol (“IP”) addresses of one or more edge computing devices. The system may maintain second information associating User Equipment (“UE”) identifiers with one or more locations. The system may receive a request, from a UE, including an identifier of the UE and a URL, may identify a location of the particular UE based on the identifier of the particular UE, and may compare the URL to the URLs included in the first information. The system may select a particular edge computing device based on the location of the particular UE, and may output, in response to the request, a particular IP address of the selected edge computing device.

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: Systems and methods described herein provide an application function and interface for a Network Data Analytics Function (NWDAF) to receive, from User Equipment (UE) devices, user data for edge applications. An NWDAF receives an analytics request for user analytics for an edge application and sends, to an Edge Analytics Engine (EAE) associated with an edge location, a data request based on the analytics request. The EAE receives user data from an Edge Enabler Client (EEC) on the UE device that is connected to the edge location. The EAE forwards the user data to the network device. The NWDAF receives the user data responsive to the analytics request and generates an analytics report based on the user data.

Abstract: A computer device may include a memory storing instructions and processor configured to execute the instructions to provide a test configuration to a plurality of multi-access edge computing (MEC) devices; collect test results associated with the provided test configuration from the plurality of MEC devices; and obtain capability information associated with particular ones of the plurality of MEC devices. The computer device may be further configured to generate a test report that relates one or more parameters included in the test results and the obtained capability information to particular ones of the plurality of MEC devices; and use the generated test report to select a MEC device from the plurality of MEC devices for a user equipment (UE) device requesting an application session.

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: An application client on a user device receives an internal request from within the application client. The internal request is associated with edge application device(s) hosted by a computing platform. In response to the internal request, the application client obtains an authorization token from the computing platform and initiates an edge discovery request to the computing platform using the authorization token. In response to the edge discovery request, the application client receives connection information of a particular edge application device among the edge application device(s) that is identified for the application client by the computing platform. The application client establishes a connection between the application client and the particular edge application device using the connection information of the particular edge application device.

Abstract: A device may include a memory storing instructions and processor configured to execute the instructions to receive, by a first blockchain node and via a first base station, a message from a first Internet of Things (IoT) device to a second IoT device, wherein the device corresponds to a first multi-access edge computing (MEC) device located in a first MEC network associated with the first base station. The processor may be further configured to authenticate, by the first blockchain node, the first IoT device using a blockchain associated with a group of IoT devices and send, by the first blockchain node, the message to a second blockchain node in a second MEC device in a second MEC network associated with a second base station servicing the second IoT device, in response to authenticating the first IoT device using the blockchain associated with the group of IoT devices.

Abstract: An illustrative latency service system identifies, in response to a request by a user equipment (UE) device for performance of a distributed computing service, a latency performance level to which the UE device is subscribed. The system obtains real-time latency performance data for a distributed computing network that is to perform the distributed computing service for the UE device in response to the request, and, based on the real-time latency performance data, determines a characteristic of a geographic zone in which the UE device is located. The characteristic is associated with latency performance that the distributed computing network is capable of providing in the geographic zone. Based on the latency performance level and the characteristic of the geographic zone, the system arranges for the performance of the distributed computing service for the UE device by the distributed computing network. Corresponding methods and systems are also disclosed.

Abstract: An exemplary edge compute orchestration system that is communicatively coupled with a set of edge compute nodes in a communication network accesses performance data aggregated by a particular edge compute node of the set. The performance data includes a performance metric and geolocation data detected by a user equipment (UE) device communicatively coupled to the communication network. The edge compute orchestration system integrates the performance data into a geolocation-indexed performance dataset representative of detected performance metrics, indexed by geolocation, for the communication network. Then, based on the geolocation-indexed performance dataset, the edge compute orchestration system selects the particular edge compute node for performance of an edge compute task. Corresponding systems and methods are also disclosed.

Abstract: A device receives, from a first compute instance, a Remote Latency Call, that includes a target latency measure, a function, and one or more arguments for the function. The device clusters a plurality of compute instances into multiple clusters of compute instances based on a respective latency measure associated with each compute instance of the plurality of compute instances, and determines a first cluster of compute instances from the multiple clusters of compute instances that satisfies the target latency measure. The device causes a second compute instance within the first cluster of compute instances to execute the function, using the one or more arguments, and return one or more results.

Abstract: An illustrative multi-access server orchestration system determines a subset of a set of multi-access servers associated with a communication network. The subset corresponds to a service area of a network anchor point through which network traffic on the communication network is routed to a client device. The multi-access server orchestration system orders the multi-access servers included within the subset to form an ordered listing of multi-access servers from a most-preferred to a least-preferred multi-access server for fulfilling a service request for the client device. The ordered listing designates a first multi-access server included in the subset and located more proximate to the network anchor point than to the client device to be more highly preferred for fulfilling the service request than a second multi-access server included in the subset and located more proximate to the client device than to the network anchor point. Corresponding methods and systems are also disclosed.

Abstract: Systems and methods provide a MEC policy optimization service. A network device applies, in a first edge cluster of the application service layer network, a policy for an application service that supports a customer application; receives network performance data related to execution of the application service; identifies, based on the network performance data, an improved policy to optimize the first policy for the customer application in the first edge cluster; and sends a model of the improved policy to a central network device for the application service layer network.