Abstract: A method, a network device, and a non-transitory computer-readable storage medium are described in relation to an edge cloud management service. The edge cloud management service may automate the provisioning, maintenance, supervision across multi-vendor network devices in a private/enterprise environment. Further, the edge cloud management service may provide abstraction and normalization services across multi-vendor components and enable KPI monitoring, location data, edge discovery metrics, end-to-end latency computation across various cloud service provider technologies.

Abstract: A method, a network device, and a non-transitory computer-readable storage medium are described in relation to an edge cloud management service. The edge cloud management service may automate the provisioning, maintenance, supervision across multi-vendor network devices in a private/enterprise environment. Further, the edge cloud management service may provide abstraction and normalization services across multi-vendor components and enable KPI monitoring, location data, edge discovery metrics, end-to-end latency computation across various cloud service provider technologies.

Abstract: One or more computing devices, systems, and/or methods for latency evaluation and management resolution are provided. A fingerprint for traffic flow over a communication network from an application executing on a device to a multi-access edge (MEC) server instance hosted by a MEC platform may be identified. The fingerprint may be used to track the traffic flow between the application and the MEC server in order to measure round trip time latencies of the traffic flow. In response to a round trip time latency violating a latency management policy, segment latencies along segments of a communication travel path of the traffic flow from the device to the MEC platform may be measured. A management resolution function may be performed based upon one or more of the segment latencies exceeding a threshold.

Abstract: One or more computing devices, systems, and/or methods for latency evaluation and management resolution are provided. A fingerprint for traffic flow over a communication network from an application executing on a device to a multi-access edge (MEC) server instance hosted by a MEC platform may be identified. The fingerprint may be used to track the traffic flow between the application and the MEC server in order to measure round trip time latencies of the traffic flow. In response to a round trip time latency violating a latency management policy, segment latencies along segments of a communication travel path of the traffic flow from the device to the MEC platform may be measured. A management resolution function may be performed based upon one or more of the segment latencies exceeding a threshold.

Abstract: A device may receive location data identifying a location of a network repeater and an identifier of a base station serving the network repeater, and may identify, based on the identifier of the base station, a first set of gNodeBs anchored to the base station. The device may identify, based on the location data, a second set of gNodeBs from a data structure, and may compare the first set of gNodeBs and the second set of gNodeBs to determine a list of gNodeBs included in the first set of gNodeBs and the second set of gNodeBs. The device may rank the list of gNodeBs, based on coverage projection recommendations, to generate a ranked list of gNodeBs, and may receive, from the data structure, configuration parameters for the ranked list of gNodeBs. The device may provide the configuration parameters for the ranked list of gNodeBs to the network repeater.

Abstract: A device may receive location data identifying a location of a network repeater and an identifier of a base station serving the network repeater, and may identify, based on the identifier of the base station, a first set of gNodeBs anchored to the base station. The device may identify, based on the location data, a second set of gNodeBs from a data structure, and may compare the first set of gNodeBs and the second set of gNodeBs to determine a list of gNodeBs included in the first set of gNodeBs and the second set of gNodeBs. The device may rank the list of gNodeBs, based on coverage projection recommendations, to generate a ranked list of gNodeBs, and may receive, from the data structure, configuration parameters for the ranked list of gNodeBs. The device may provide the configuration parameters for the ranked list of gNodeBs to the network repeater.