A network node, such as a quality of experience QoE orchestrator, start monitors (400) data traffic related to a terminal device, in order to detect (402) a data flow related to an application session. The network node derives (403) resource requirement information defining a required QoE level to be provided to the terminal device regarding the application session. The network node performs (404) QoE measurements to obtain information on QoE experienced by the terminal device regarding the application session. Based on the QoE measurements, the network node executes one or more actions in order to enforce (405) the quality of experience QoE of the application session to meet the resource requirement.

In one embodiment, an application server to achieve improved quality of service (QoS) for content delivery in a communication network is disclosed. The application server receives a request from a client device to deliver content to the client device. The application server determines a relative priority of each of a plurality of content delivery servers in the communication network based on at least one of one or more parameters and a configuration file. The application server identifies at least one content delivery server from the plurality of content delivery servers based on relative priority. The application server identifies a shortest path for the content delivery between the identified at least one content delivery server and the client device based on one or more pre-defined rules. The application server further transmits the content from the identified at least one content delivery server to the client device via the identified shortest path.

There is provided systems, methods and computer program products for dynamically allocating bandwidth of a network in a transportation network. The system comprises a module (103) that receives schedule data including data defining a plurality of different journeys and data defining an equipment type. The module (103) identifies an event type for each journey based on the schedule data and generates a request to change the bandwidth allocation of the network based on a first event type and the equipment type. This advantageously enables the system to efficiently allocate bandwidth to a plurality of customers without exceeding a network bandwidth capacity.

A flow tagging technique includes tagging a data flow at a plurality of points in the data flow. For example, the data flow can be tagged at a socket and at a proxy manager API. By tagging the data flow at multiple points, it becomes possible to map network service usage activities to the appropriate initiating applications.

In one embodiment, a networking device reroutes traffic in a network from a first path to a second path, based on a prediction that the first path will not satisfy a service level agreement associated with the traffic. The networking device enters a fast monitoring state during which the networking device performs fast probing of the first path and of the second path onto which the traffic was rerouted. The networking device makes, based on the fast probing, a determination as to whether the first path would have violated the service level agreement and whether the second path violates the service level agreement. The networking device enacts a routing decision for the traffic by applying a routing policy to the determination.

In one embodiment, a networking device reroutes traffic in a network from a first path to a second path, based on a prediction that the first path will not satisfy a service level agreement associated with the traffic. The networking device enters a fast monitoring state during which the networking device performs fast probing of the first path and of the second path onto which the traffic was rerouted. The networking device makes, based on the fast probing, a determination as to whether the first path would have violated the service level agreement and whether the second path violates the service level agreement. The networking device enacts a routing decision for the traffic by applying a routing policy to the determination.

The operator load is reduced while satisfying a service quality specification as far as possible. A handling procedure inquiry unit 121 acquires a handling procedure group including at least one handling procedure regarding a failure, a handling/recovery influence inquiry unit 122 acquires a degree of influence of performing, with respect to each handling procedure of the handling procedure group, the handling procedure, a handling procedure prioritization unit 123 selects the handling procedure to be performed based on whether or not a worker is needed and the degree of influence, a countermeasure selection unit 124 assigns the selected handling procedure to an automatic handling control unit 13, a planned maintenance control unit 14, or an immediate action control unit 15 that can perform the handling procedure.

A distributed storage system monitors one or more system performance metrics and one or more client performance metrics related usage of the distributed storage system, including a read latency metric, a write latency metric, a total input/output (I/O) operations per second (IOPS) metric, a read IOPS metric, a write IOPS metric, an I/O size metric, a total bandwidth metric, a read bandwidth metric, a write bandwidth metric, a read/write ratio metric or statistical measures thereof over a period of time. When the distributed storage system is determined to be in an overload condition (e.g., when a system load value, calculated based on the performance metrics, exceeds a threshold), the distributed storage system independently throttles access to one or more components of the distributed storage system by one or more of multiple clients performing I/O operations to the distributed storage system based on their respective contribution to the overload condition.

A radio access network (RAN) node can receive, from a user equipment (UE), a request to establish a session associated with a low-latency service level agreement (SLA). The session can be mapped to a radio bearer associated with a network slice configured to support the low-latency SLA, wherein the network slice can include a RAN portion and a core network portion that are co-located at a RAN edge to support the low-latency SLA. The RAN node can provide information related to the radio bearer to a distributed unit (DU) associated with the RAN portion of the network slice and route traffic associated with the session through the network slice configured to support the low-latency SLA via the radio bearer mapped to the session. As such, the session can have a context maintained in the RAN portion and the core network portion of the network slice.

A system for troubleshooting network problems is disclosed. A model can use demographic information, network usage information, and network membership information to determine an importance of a problem. The importance of the problem for the user who reported the problem, a number of other users affected by the problem, and the importance of the problem to the other users can be used to determine a priority for resolving the problem. Before and after a work order is executed to resolve the problem, network metrics can be gathered, including aggregate network metrics, and automatically presented in various user interfaces. The analysis of the metrics can be used to update a database of which work orders are assigned in response to which problems.