Intelligent ticketing and data offload planning is provided. A data center receives a ticket request from a vehicle requesting to perform a data upload of vehicle data over a communications network. An optimizer is utilized to generate a ticket, the ticket specifying a time and a location for the vehicle to perform the data upload. The ticket is received from the vehicle. The ticket is validated to ensure that the vehicle should still perform the data upload. The vehicle is indicated to perform the data upload over the communications network responsive to the optimizer confirming the data upload to proceed. The data upload is stored to a storage of the data center.

Example methods and systems for service-aware global server load balancing are described. One example may involve a first load balancer receiving, from a client device, a request to access a service associated with an application deployed in at least a first cluster and a second cluster. In response to determination that a first pool in the first cluster is associated with an unhealthy status, the first load balancer may identify a second pool implementing the service in the second cluster, the second pool being associated with a healthy status and includes one or more second backend servers selectable by a second load balancer to process the request. Failure handling may be performed by interacting with the client device, or the second load balancer, to allow the client device to access the service implemented by the second pool in the second cluster.

Example methods and systems for service-aware global server load balancing are described. One example may involve a first load balancer receiving, from a client device, a request to access a service associated with an application deployed in at least a first cluster and a second cluster. In response to determination that a first pool in the first cluster is associated with an unhealthy status, the first load balancer may identify a second pool implementing the service in the second cluster, the second pool being associated with a healthy status and includes one or more second backend servers selectable by a second load balancer to process the request. Failure handling may be performed by interacting with the client device, or the second load balancer, to allow the client device to access the service implemented by the second pool in the second cluster.

A network node and method performed thereby, for enabling determination, by a prediction function network node, of a change in QoS of a communication session of a UE. The method includes obtaining information related to the UE communication session, the information including an ID of the UE and an ID of the communication session. The method further comprises determining the target serving cell of the UE and providing the obtained information and an ID of the determined target serving cell to the prediction function network node, thereby enabling the prediction function network node to determine new QoS of the UE communication session when being served by the target serving cell. A prediction function network node and a method performed thereby, and a user equipment and a method performed thereby are also disclosed.

In some examples, a non-transitory computer-readable medium stores machine-readable instructions which, when executed by a processor, cause the processor to: collect operational data of an enterprise; identify a domain of the operational data; determine a performance metric of the domain; and generate a report based on the performance metric.

Techniques to using distributed ledgers to confirm service levels in a network routing are disclosed. Communications networks are virtualized thereby enabling software-defined networking (SDN). An SDN scheduler or allocator makes use of routing techniques where the state of the network is persisted in a form of storage that all nodes are in consensus is accurate. In one example, the SDN scheduler may generate a temporal audit trail of service level agreements (SLAs) over a network path that includes different intermediate autonomous systems from a transmitting node to a destination node. The SDN scheduler may further perform temporal enhancements of the contract, and then combine the temporal enhancements with the temporal audit trail to confirm the actual service level against the service level as prescribed in the contract.

Techniques to using distributed ledgers to confirm service levels in a network routing are disclosed. Communications networks are virtualized thereby enabling software-defined networking (SDN). An SDN scheduler or allocator makes use of routing techniques where the state of the network is persisted in a form of storage that all nodes are in consensus is accurate. In one example, the SDN scheduler may generate a temporal audit trail of service level agreements (SLAs) over a network path that includes different intermediate autonomous systems from a transmitting node to a destination node. The SDN scheduler may further perform temporal enhancements of the contract, and then combine the temporal enhancements with the temporal audit trail to confirm the actual service level against the service level as prescribed in the contract.

The present disclosure relates to a method for transferring data, in which a peripheral device and a central device are wirelessly connected in accordance with the Bluetooth Low Energy (BLE) standard and a data packet is transferred within a transfer window of a Bluetooth Low Energy data channel between the peripheral device and the central device.

The present disclosure relates to a method for transferring data, in which a peripheral device and a central device are wirelessly connected in accordance with the Bluetooth Low Energy (BLE) standard and a data packet is transferred within a transfer window of a Bluetooth Low Energy data channel between the peripheral device and the central device.

A device receives a notification indicating a failure of a first server device responsible for a primary message queue that includes messages at a time of the failure. A second server device is responsible for a standby message queue to which the messages are replicated, where a position in the standby message queue and a message time are assigned to each of the replicated messages. The device obtains a record time that identifies the message time of one of the messages that was last obtained from the primary message queue prior to the failure, compares an adjusted record time and the message time of one or more of the messages of the standby message queue to determine a starting position in the standby message queue, and processes messages obtained from the standby message queue beginning at one of the messages assigned to the position that matches the starting position.